tare

tare

Ask Claude Code where your usage went.

You hit a usage limit and don't know why. Your quota drains faster than it
used to. You suspect something is eating tokens in the background. The
records that answer all of this are already on your computer — Claude Code
keeps a log of every request it makes. tare teaches Claude Code to read
its own logs, so you can just ask.

No dashboards, no commands to learn. Install once, then ask in plain
English.

*Tare: the weight of the container, subtracted to find what's inside. Most
of what a session costs is the container — context re-sent again and again —
and that's exactly what these tools subtract.*

Read full story - https://www.kelviq.com/blog/claude-code-usage-limits-where-tokens-go/

Install

One command, in any terminal:

That's it. Nothing else to set up — no accounts, no packages, no
configuration. Start a new Claude Code session and it's live — type
/ and check that tare appears. If it doesn't, see the
troubleshooting note — on machines where
Claude Code has never installed a skill before, the installer can miss
it. (Other ways to install — by hand, for a whole team, or as a Claude
Code plugin — are in INSTALL.md.)

Then just ask

Open Claude Code and ask your question the way you'd ask a person. These all
work — the words don't have to match, complaining about your limits is
enough:

When you hit a limit
*Why did I hit my usage limit yesterday?*
*I got locked out ten minutes into my evening session — how is that
possible?*
*Did I hit the 5-hour limit or the weekly cap?*
*Why am I burning through my quota so much faster this week?*

Where your tokens go
*Where did my tokens actually go this week?*
*Which of my projects is eating my quota?*
*Which model is costing me the most?*
*What's the most expensive file Claude…