Tokens
Track, visualize, and compete on AI coding assistant token usage across Claude Code, Cursor, OpenCode, Codex, Gemini, Kimi, and Qwen. The Kardashev Scale for AI Devs.
Per-group storage attribution across the six marin-* GCS buckets.
Translation pending
DataTypeScript · PythonGitHub @Open-AthenaOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Per-user attribution and reporting for Marin GCS storage
Loading the full README. The saved excerpt is shown below.
The public preview: cells are sized by bytes and coloured by top-level prefix, with names, sizes, owners, and costs omitted. The site shows all of them to signed-in users.
Storage-usage attribution and cleanup for the Marin GCS buckets: who is using
what, and a mark & sweep workflow to reclaim space. Browse it at
[gcs.oa.dev] (Open-Athena-gated).
The identity map (cloud/src/dt_cloud/identities.yaml: handles, teams, login
aliases) is curated in-repo; it maps already-public GitHub / W&B handles to a
team bucket (oa / stanford / communal) and carries no emails or private
contact info.Read the full README ↗This branch deploys the public docs and staff-only fleet dashboard at disky.oa.dev. Each storage dashboard has its own deployment branch below.
disky maps where storage goes: scheduled scans of a store's buckets, then a treemap site with sizes over time, diffs between scans, owners and read recency. Open Athena runs four deployments, one per storage provider. Each has its own branch in this repo, and each branch merges the shared base, runsascoded/disky@cloud.
Each card is the site's own link preview, drawn from its latest scan (gcs shows its static public preview: its cards are for signed-in viewers).
| branch | site | scans |
|---|---|---|
gcs | gcs.oa.dev | Marin's GCS buckets (marin-*), with per-user ownership, read recency from access logs, and staged deletion |
cw | cw.oa.dev | Marin's CoreWeave (CAIOS) S3 buckets, with zone quotas and lifecycle rules |
hf | hf.oa.dev | the open-athena Hugging Face org: its buckets, models, datasets and spaces, including the history its storage bill counts |
r2 | r2.oa.dev | Open Athena's Cloudflare R2 buckets, including disky's own indexes |
The sites are Open-Athena-gated. Each branch's README says how its scan runs, what it changes from cloud, and where its infrastructure lives.
.github/workflows/health.yml: the hourly serving check across all four sites. It lives here because GitHub runs schedule: workflows only from a repo's default branch.cloud, including fleet/: public docs and a staff-only fleet page over the four deployments. fleet/wrangler.toml is this deployment's configuration; broker client and source tokens are encrypted Pages secrets.CI: tests the shared code before publishing. The front-door deployment workflow builds and checks preview before production; FLEET_DEPLOY_ENABLED=1 enables it after credentials are configured.fleet-update.yml, FLEET_POST_ENABLED=1) is not enabled until source tokens, sign-in and the first post are verified; the existing healthcheck keeps its own schedule.runsascoded/disky, branch cloud: the scanning engine, the dt-cloud overlay, the site, and the specs.