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

usagecut

v1.1.6

Published

Scan your Claude Code setup and see exactly how many tokens you waste and where. By ClockedCode. Not affiliated with Anthropic.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

neozinoneozino

Keywords

claudeclaude-codetokensusageoptimize

Readme

UsageCut

See exactly how many tokens you waste in Claude Code, and where. Then cut them.

npm license runs locally

npx usagecut

No install. No account. No API key. Runs entirely on your machine.

UsageCut demo - npx usagecut scans your Claude Code setup, shows the waste, and cuts it

ccusage tells you what you spent. UsageCut shows you what you are wasting, and cuts it.

Claude Code re-sends your whole conversation on every turn, so duplicate file reads, idle MCP servers, and a bloated CLAUDE.md quietly tax every single message, which is what drains your weekly limit faster than the work you actually did. UsageCut reads your real session history, finds that waste, and shows you a clean visual report of where it goes.

What it does

  • Reads your Claude Code setup and session transcripts locally - config, MCP servers, CLAUDE.md, and your ~/.claude history.
  • Measures your waste by replaying your own tool outputs through the exact shipped trimmer, so the number is measured, not estimated.
  • Finds the specific culprits: idle MCP servers loaded into every session, oversized always-loaded instructions, and the same files read again and again.
  • Renders a visual report with a setup grade, where your tokens go, and how you rank against other developers scanned so far.
  • Optimizes it for you, for free - disable idle servers, slim and re-scope CLAUDE.md, and install a lossless live trimmer. Every change is backed up, diffed, and reversible with one command.

Usage

npx usagecut          # scan your setup and open your visual web report
npx usagecut --json   # print the raw aggregate payload, no upload

npx usagecut apply    # apply the free optimizations (backed up + reversible)
npx usagecut status   # show what is currently applied
npx usagecut revert   # undo every change, restoring your original setup

Privacy

Your raw code, prompts, and logs never leave your machine. The scan runs locally and uploads only aggregate counts - numbers and one-letter grades - to render your web report. Nothing else is transmitted, and there is no account to create. The scanner is open source, so you can read exactly what it does before you run it.

How it cuts tokens

UsageCut is lossless by design. It never makes Claude dumber and never reroutes your API key or your code. The levers:

  • Live trimmer - a local hook that losslessly shrinks bulky, repeated tool output as it appears (collapses duplicate reads, strips junk). The big one.
  • Disable idle MCP servers - detected from your real transcripts, including sub-agent transcripts, so a server is only flagged when it was truly never called.
  • Slim CLAUDE.md - trim and re-scope always-loaded instructions, kept verbatim, so they only load where they are actually needed.

Honest about the numbers: setup fixes alone are a modest cut; the live trimmer is where most of the savings live on token-heavy sessions. The free scan measures your real sessions and shows your number - no billboard percentages.

Options and environment

  • --json - print the raw aggregate payload instead of uploading.
  • USAGECUT_API_URL - override the report endpoint (defaults to https://www.usagecut.com).
  • USAGECUT_TOKEN - claim token from the website scan page, so that page shows your scan automatically.

About

UsageCut is a free tool by ClockedCode. It is free because it is genuinely useful on its own - if you want to push Claude Code much further, that is what ClockedCode is for.

Not affiliated with Anthropic. "Claude" and "Claude Code" are trademarks of Anthropic.

License

MIT. See LICENSE.