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 →filterslast 30d · codex
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 |
|---|---|---|---|---|---|---|
| 1– |  @VinayakRai5✓ | 23.3B | $30,187 | 0d | ||
| 2– |  @veerLakshya✓ | 19.4B | $3,891 | 0d | ||
| 3– |  @Parth080✓ | 15.1B | $11,085 | 11d | ||
| 4– |  @AryanTN05✓ | 313M | $20 | 0d | ||
| 5– |  @iyashjayesh✓ | 149M | $316 | 0d | ||
| 6– |  @manishreddy123✓3w | 97.0M | $86 | 0d | ||
| 7– |  @Sanket758✓ | 33.4M | $1 | 1d |
- codex
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.