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✓ | 27.2B | $0 | 0d | ||
| 2▲2 |  @veerLakshya✓ | 16.5B | $0 | 0d | ||
| 3▲2 |  @Parth080✓ | 5.62B | $4,623 | 5d | ||
| 4▼2 |  @iyashjayesh✓ | 3.67B | $0 | 0d | ||
| 5▼2 |  @manishreddy123✓ | 2.27B | $1,106 | 0d | ||
| 6– |  @Rupam-M✓3w | 961M | $0 | 0d | ||
| 7– |  @AryanTN05✓ | 843M | $3 | 0d |
- 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.