The board
opt-inEveryone who ran tokenchit publish, or a bare tokenchit generate, which ends by calling it. A usage count over the selected window, not a skill score.
Get your own card →filtersthis year · claude code
GitHub sign-in proves the handleself-reported, handle unprovedNeither audits the figures — see the notes below the table.
| rank | developer | agent mix | last 30d | tokens | equiv. cost | streak |
|---|---|---|---|---|---|---|
| 26– | — | 1.29B | $1,710 | 0d | ||
| 27– | — | 1.07B | $270 | 0d | ||
| 28– | — | 1.02B | $559 | 0d | ||
| 29▲4 | 435M | $135 | 1d | |||
| 30▼1 | — | 416M | $298 | 0d | ||
| 31▼1 | — | 345M | $83 | 0d | ||
| 32▼1 | — | 292M | $254 | 0d | ||
| 33▼1 | — | 13.1M | $10 | 0d | ||
| 34– | @bharath-1720cli6w | — | 909M | $791 | 0d | |
| 35– | @homingoscli6w | — | 908M | $790 | 0d |
- claude-code
How this is ranked
Verified rows first, then tokens over the selected window. Signing in is the only thing that ties a row to a GitHub account, so it is the only thing that can carry a position — an unverified row still appears with its figures, it just cannot outrank a verified one. Every column covers the same window as the rank.
A cli badge means the numbers were self-reported without a GitHub sign-in; those rows stay on the board rather than being hidden, because a visible unverified row is more honest than a quietly filtered one. Streak is the current run of active days, which is not a windowed figure. Submissions far outside the range of real usage are held for review and do not appear until a person has looked. Figures are self-reported and bounded for plausibility, not audited.