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

claude-cooked

v0.1.0

Published

Get roasted for how you use Claude Code. Your Cooked score, what your tokens would cost at API prices, a roast from your own Claude, a shareable receipt and roast battles with friends. Runs locally; your prompts never leave your machine.

Readme

claude-cooked

Get roasted for how you use Claude Code.

npx claude-cooked

It reads your local Claude Code history, gives you a Cooked score out of 100, has your own Claude roast you with your real numbers, tells you how to cut your usage, and prints a receipt you can share.

claude-cooked  80/100 FULLY COOKED  The Context Hoarder
"Pays $20 a month for $9,234 of compute and still types 'dude' at me 340 times."

THE ROAST
  * Your first 4 messages to the most capable AI on Earth were "hey". It took you 4 tries to say hi.
  * You've typed /quit 433 times. Claude has never once quit on you.
  * 1,065 prompts after midnight, the latest at 4:58am. Your sleep schedule is "whenever the rate limit hits".
  ...

What you get

  • The roast. If Claude Code is installed, your own Claude writes it (about a cent of usage, no API key). If not, built-in roasts fill in your numbers. Every line quotes a real stat.
  • The evidence. All-time tokens and what they would cost at API prices, month by month, model by model, your hours, streaks, night-owl share, favourite words, most-used commands, tools and lines written.
  • The redemption arc. Fixes ranked by how much they'd save: when to start fresh, what loads before you type, which work can move to a cheaper model.
  • A receipt. Opens in your browser with a Download PNG button.
  • A battle code. Send it to a friend; they run npx claude-cooked --vs <code> and Claude roasts you both.

Options

npx claude-cooked                 medium roast
npx claude-cooked mild|ramsay     spice level
npx claude-cooked stats           numbers and tips only, no roast
npx claude-cooked --vs <code>     roast battle
  --name <name>    your name on the receipt and battle code
  --no-claude      built-in roasts only
  --no-open        don't open the browser
  --json           everything computed, as JSON (includes folder paths and your first prompt: keep it private)
  --dir <path>     Claude config folder (default $CLAUDE_CONFIG_DIR or ~/.claude)

Privacy

Everything is computed on your machine. Your prompts and files are never uploaded.

When Claude Code is installed, the numbers on your card (counts, dollars, hours, a word from a fixed list like "dude", the country your timezone suggests, and the --name you pick, if any) are sent to your own Claude to write the roast. Your prompts, file names and project names never are. The receipt and battle code hold only those numbers, so they're safe to post.

Where the numbers come from

  • stats-cache.json: Claude Code's own all-time token totals and daily activity
  • history.jsonl: every prompt you've typed, with timestamps
  • projects/**/*.jsonl: full session transcripts (Claude Code deletes these after 30 days by default)
  • your plan, from .credentials.json or ~/.claude.json

Most usage tools only read the transcripts, so they forget everything older than a month. This one reads all three.

"API price" is what your tokens would cost with an API key, using list prices (see PRICES in stats.js). On a subscription you don't pay that; it's a measure of how hard you're leaning on your plan.

The Cooked score

Five parts, 20 points each, computed from the card so battles are fair:

| Part | Measures | |---|---| | burn | API-price value per month | | night | share of prompts between midnight and 5am | | hoard | average context per request | | manners | please and thanks per 100 prompts (fewer = more cooked) | | chaos | /usage checks, interrupts, corrections, model-hopping |

Requires Node 18.17+. Zero dependencies. MIT.