npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

tokenbbq

v0.7.1

Published

Local dashboard for AI coding CLI token usage, estimated costs, and project/model breakdowns

Readme

TokenBBQ

npm version License: MIT

TokenBBQ is a local dashboard for AI coding tool usage. It reads the local data your tools already write and turns it into absolute numbers: tokens, estimated cost, model and project breakdowns, daily/monthly trends, and local Claude/Codex rate-limit snapshots when those tools expose them.

Run it directly with npx:

npx tokenbbq@latest

No install. No config. No API key. No TokenBBQ cloud.

Dashboard

TokenBBQ starts a local server and opens the dashboard in your browser. By default it uses localhost:3005; pass --port=<n> to choose another port.

npx tokenbbq@latest
npx tokenbbq@latest --port=8080
npx tokenbbq@latest --no-open

Dashboard highlights:

  • estimated cost, total tokens, active days, cost/day, and top model
  • daily token usage timeline by source
  • cost split by provider
  • top models by cost
  • monthly trend
  • activity heatmap
  • project breakdowns
  • expandable daily table with per-source detail
  • time filters for short-term and long-term usage views
  • live refresh while the dashboard is running

Supported Tools

| Tool | What TokenBBQ reads | What you get | |---|---|---| | Claude Code | local usage files | tokens, estimated cost, models, sessions, project context when available | | Codex | local usage files | tokens, estimated cost, and local rate-limit snapshots when present | | Gemini | local usage files | tokens, models, and project context when available | | OpenCode | local usage data | tokens, estimated cost, and project/worktree context | | Amp | local usage data | tokens, estimated cost, and cache-token details when available | | Pi-Agent | local usage files | tokens and emitted cost fields |

Default locations are detected automatically. Environment variables can override source paths when your tools are installed somewhere else:

| Tool | Override | |---|---| | Claude Code | CLAUDE_CONFIG_DIR | | Codex | CODEX_HOME | | Gemini | GEMINI_DIR | | OpenCode | OPENCODE_DATA_DIR | | Amp | AMP_DATA_DIR | | Pi-Agent | PI_AGENT_DIR |

Options

npx tokenbbq                # Open the local dashboard in your browser
npx tokenbbq --port=8080    # Use a custom dashboard port
npx tokenbbq --no-open      # Start the server without opening the browser
npx tokenbbq --help         # Show help

TokenBBQ is dashboard-only. The supported product surface is the local browser dashboard started through npx tokenbbq.

How It Works

TokenBBQ does not proxy model traffic and does not watch your network.

  1. It reads the local usage data your AI coding tools already write.
  2. It persists normalized events under your local TokenBBQ data directory.
  3. It turns those events into absolute token counts and estimated cost.
  4. It groups usage by day, month, source, model, and project.
  5. It serves the result through a local browser dashboard.

For Codex, TokenBBQ reads the latest local rate-limit snapshot when Codex has written one.

Privacy

TokenBBQ is local-first:

  • The dashboard reads local files and serves localhost.
  • There is no TokenBBQ account.
  • There is no TokenBBQ backend.
  • Usage data is not uploaded to TokenBBQ.
  • Model pricing is fetched from LiteLLM when available.

Your AI coding logs can contain project names and code context. TokenBBQ's job is to make that local data understandable, not to send it somewhere else.

Development

npm install
npm run dev
npm run test
npm run build

npm run dev starts the dashboard via tsx. npm run build produces the publishable dist/index.js package entry used by npx tokenbbq.

Guides

Credits

TokenBBQ builds on data-loading patterns from ccusage by @ryoppippi. ccusage is the recognized predecessor in this space; TokenBBQ extends the idea across more tools, a browser dashboard, project views, and rate-limit snapshots where available.

Contributing

See CONTRIBUTING.md for development setup and guidelines for adding new tools.

Support

Buy me a Token:

ko-fi

License

MIT (c) offbyone1