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

cc-save

v1.0.0

Published

How much money has Claude's prompt cache saved you? Cache savings analysis — the real dollar value of cache_read vs fresh input tokens.

Readme

cc-save

How much money has Claude's prompt cache saved you?

Calculates the real dollar value of prompt caching — the difference between what you paid and what you would have paid if every cached token was billed as fresh input.

Usage

npx cc-save
npx cc-save --json

Override pricing (default: Sonnet 4.6):

npx cc-save --input=3.00 --cache-r=0.30 --cache-w=3.75 --output=15.00

Or open index.html in a browser and drag in .jsonl files.

Metrics

  • Savingscache_read_tokens × (input_price - cache_read_price) / 1M
  • Cache hit rate — % of input tokens served from cache vs fresh
  • Cost breakdown — actual vs hypothetical total
  • Per-session average — savings and cost per session

Sample output

cc-save — How much money has Claude's prompt cache saved you?

  $59.7K saved by prompt caching
  86% of what you'd pay without caching

Cost breakdown  (519 sessions, 219,669 turns)
  Input (fresh)    $15.35    5.1M tokens × $3.00/1M
  Cache reads      $6.6K    22.1B tokens × $0.30/1M
  Cache written    $2.5K   668.7M tokens × $3.75/1M
  Output          $291.82   19.5M tokens × $15.00/1M
  ──────────────────────────────────────────
  Actual total     $9.4K
  Without caching $69.1K   (if cache reads billed as fresh input)

Cache efficiency
  Hit rate         97%  of total input tokens served from cache
  Cache multiplier 10×  cheaper per token
  Per session      $115.00 saved / $18.20 actual cost

Prompt caching saved you $59.7K (86% of your hypothetical bill).

License

MIT