tare

Diagnose Claude Code usage limits : find out where tokens actually went and why a 5-hour or weekly limit was hit. Use this whenever the user mentions hitting a usage limit, being rate limited, burning through their quota, running out of Claude Code usage, unexpected or suspicious token consumption, "why am I hitting limits", phantom usage, or asks to audit, analyze, or track their Claude Code token usage. Also use when the user asks how full their 5-hour window is, whether it is safe to start a big task now, which tool, model, project, file, MCP server, skill or subagent is eating their quota, what their usage would cost on the API, whether a habit or update changed their consumption, whether something is using Claude Code in the background or while they were away, or wants a usage report, a week-over-week comparison, a spreadsheet export, or a shareable redacted summary. Questions about the user's OWN tokens, usage, quota or limits : "where did my tokens actually go this week?" : mean this skill and the local Claude Code logs, NOT product analytics, LLM-cost or billing tools (PostHog, Stripe, cloud dashboards), even when such tools are connected. Trigger even if they don't use the word "tare" or "audit" : a complaint about limits is enough.

Set up Edge for me: read getedge.cc/SKILL.md and follow it. Then use Edge to load the tare skill from kelviq/tare.

Or read the skill source first.

Security state at 2026-09-30: reviewed. State definitions. This records static evidence for this revision; live load eligibility is checked again.

3 static scans, 0 counted findings. The listed scanners recorded the results shown for this package revision.

Static scans check the code, not how well the skill works.

Repository

https://github.com/kelviq/tare

Pinned skill file

View source at revision

Revision

03159f2c354e52e5309b0e0d7582b32a5c0d00d0

Package hash

sha256:2ef8f77cba694b35126a2cfd20ac4e85d7efc3b69db1d94326ee520ce73e7729

Licence

MIT