tare

About tare

Diagnose Claude Code usage limits—find out where tokens actually went and why a 5-hour or weekly limit was hit. Use 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.