// HACKER NEWS — CYBERSECURITY
Show HN: My Claude quota ran out in 10 minutes, so I made a tool to find out why
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.
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.)
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:
I got locked out ten minutes into my evening session — how is that
possible?
Why am I burning through my quota so much faster this week?
What's the most expensive file Claude keeps re-reading?
How much did that giant session yesterday actually cost me?
Is it safe to start a big refactor now, or should I wait for my window to
clear?