pickfit

BrowseDeveloper CLIs

ccclub.dev

Compare coding-agent token usage and costs with friends in shared leaderboard groups.

Tested on Linux

Use it

Linux x86_64

You need first

  • Needs the network
  1. Install ccclub globally via npm

    npm install -g ccclub && ccclub --version

Check that it works

npm install -g ccclub && ccclub --version

The output should contain “0.9.8”.

First thing to try

ccclub sources

Run ccclub init to set up your profile and group, then run ccclub to see your group's leaderboard.

What it does

  • Create a group and compare usage
    How to use it
    1. Run ccclub init and enter your name when asked.
    2. Run ccclub to see the leaderboard and your group's dashboard link.
    3. Run ccclub --json to get the rankings as JSON.
    Tested
  • Track coding agent token usage and costs
    How to use it
    1. Run ccclub sources to see which coding agents are tracked.
    2. Run ccclub sync && ccclub show-data to upload your usage and see the token counts that were sent.
    Tested
  • View the live group dashboard page
    Not shown working
  • Show Claude Code usage and rank in the status line
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 2 of 4 features work
  4. Works offline

Good for

  • compare Claude Code usage with friends in a group
  • track coding agent token usage, costs and active status
  • show the group usage leaderboard
  • audit exactly what usage data gets uploaded

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.9.8

Differences the test machine hit

  • README: npx ccclub init
    In the test: installed with npm install -g ccclub (same package as npx ccclub) so ccclub is on PATH; npx ccclub init runs the same code

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.