For Claude Code and other coding agents

Spend fewer tokens.
Lose nothing.

Two tools that work together. Tokenmeter shows where your Claude Code tokens go, live. TokenDiet cuts what your instructions add to every request, without making your agent any less capable.

Both run on your computer. Nothing is sent anywhere.

Instructions per request

Before TokenDiet2,865 tokens

After TokenDiet409 tokens

Claude Code on the demo project that ships with TokenDiet. Nothing the agent needs was removed.

Two tools, one goal

TOKENMETER

Free · open source (MIT) · Claude Code plugin

  • Live pane in every session: tokens, context fill, plan limits
  • Local dashboard with 90 days of history
  • Counts each response once, unlike tools that sum every log line
Explore Tokenmeter
TOKENDIET

$15 one-time · Agent Skill

  • Measures what 7 coding agents load into every request
  • Finds repeated, stale and misplaced instructions
  • Applies lossless fixes, with your approval and a backup
Explore TokenDiet

How they work together

Every request your agent sends carries the whole conversation and your instruction files. Tokenmeter makes that visible; TokenDiet makes it lighter.

  1. See it

    Tokenmeter shows each session's tokens and context fill, and suggests a diet when the context passes half the window or the prompt cache keeps missing.

  2. Trim it

    TokenDiet measures your CLAUDE.md, AGENTS.md and rules files, proposes lossless fixes, and applies the ones you approve.

  3. Track it

    Each audit shows up in Tokenmeter's dashboard as that project's instruction weight, before and after.

TokenDiet audit report in a terminal: Claude Code loads about 2,865 tokens of instructions per request in the demo project, about 409 after safe fixes, followed by findings such as a release process section and a 32-line code sample in CLAUDE.md
A TokenDiet audit of the demo project included with the skill.

On the demo project

2,865 → 409tokens of instructions Claude Code loads per request
631 → 233tokens of rules Cursor loads per request
8findings, each explained with its fix

Measured on the demo project that ships with TokenDiet. Your results depend on your setup. Counts are estimates within about ±20%.

Private by design

Runs locally

Both tools read files on your computer and send nothing anywhere. No account, no API key.

You stay in control

TokenDiet asks before every change and backs up every file it edits. One command undoes it.

No tracking here either

This website sets no cookies and loads nothing from other sites. See the privacy policy.

Frequently asked questions

Do I need both tools?

No. Each works on its own. Tokenmeter shows where your tokens go; TokenDiet reduces what your instructions add to every request. Used together, Tokenmeter also shows each TokenDiet audit and suggests one when a session gets heavy.

Is Tokenmeter really free?

Yes. Tokenmeter is open source under the MIT license, with the code on GitHub. TokenDiet is a separate, paid skill.

Which agents do they support?

Tokenmeter works with Claude Code. TokenDiet's audit covers Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf and Cline, and runs in any agent that supports Agent Skills (SKILL.md). Its session usage check needs Claude Code.

Does anything leave my computer?

No. Both tools run locally, read files on your machine, and send nothing anywhere. This website doesn't use cookies or tracking either.

What does "lossless" mean here?

TokenDiet only removes repetition and noise, or moves instructions so they load when they are needed instead of on every request. It never lowers your model, effort or thinking, and asks before every change.