Claude Code leaderboards, compared
Ranking Claude Code usage has become a small genre of its own. The tools differ mainly on two axes: who sees the board (the public, or just your group) and how data gets there (manual submission, or automatic sync). Disclosure: ccclub is our project; descriptions of the others are based on their public docs as of July 2026.
The options
viberank — a public community leaderboard. You sign in with GitHub and submit your usage (generated via ccusage); rankings by cost and tokens. Good if you want your numbers visible in a global community.
ccgather — an open-source public leaderboard and community. You sync usage with its CLI (npx ccgather) and get global and country-level rankings, levels and badges, an activity heatmap, and an AI-translated community feed. The most community-oriented of the group.
tokenleaders — a lightweight public Claude usage ranking; simple and fun rather than feature-heavy.
Other public boards in the same vein: clawd.gg (ranks prompts, tokens, and lines of code) and CCLeaderboard (CLI submission, daily and all-time rankings).
ccclub — private-first. You create a group with npx ccclub init, friends join with a 6-letter code, and the board updates automatically from local logs (Claude Code session-end hook; background sync for Codex, OpenCode, Amp, Grok, Pi). No accounts. Each group gets a live web dashboard, and there's an opt-in global board if you do want a public ranking. Only numeric summaries are uploaded — no prompts, code, or file paths.
Side by side
| viberank | ccgather | tokenleaders | ccclub | |
|---|---|---|---|---|
| Audience | Public | Public | Public | Private group (opt-in global) |
| Account | GitHub | Sign-up | Varies | None |
| Data flow | Manual submission | Submission/sync | Submission | Automatic sync |
| Agents beyond Claude Code | Some | Claude-focused | Claude-focused | Codex, OpenCode, Amp, Grok, Pi |
| Web dashboard per group | — | — | — | Yes |
How to choose
- Want the world to see your rank? viberank or ccgather — that's exactly what they're for.
- Want a board for people you actually know? ccclub — private groups with auto-sync were the design goal.
- Don't want a leaderboard at all? You may just want usage reports — see how to check Claude Code usage or ccusage.
A fair caveat that applies to all of these, ours included: token count measures activity, not productivity. Leaderboards are for curiosity and fun — treat them that way.
FAQ
What's the difference between viberank and ccclub?
viberank is a public community leaderboard you submit usage to (GitHub sign-in, data via ccusage). ccclub is private-first: a group of friends with an invite code, automatic sync from local logs, no accounts, plus an opt-in global board.
Do these leaderboards see my code or prompts?
They rank usage metadata, not content. ccclub uploads only numeric summaries (tokens, estimated cost, model names, turn counts) — verifiable with ccclub show-data. For other tools, check their docs for what a submission includes.
Which leaderboard supports agents other than Claude Code?
ccclub tracks Claude Code, Codex, OpenCode, Amp, Grok, and Pi on one board and shows each member's agent mix. Most other leaderboards are Claude-focused.
Is a token leaderboard a good measure of productivity?
No — it measures activity and spend, not output quality. These tools (ccclub included) are best treated as curiosity and friendly competition, not performance metrics.
Last updated 2026-08-04. Corrections welcome on GitHub.