I wanted to know which project was eating my Claude Code quota

I interviewed a user who sought to understand which project was consuming their Claude Code quota. The user discovered that Claude Code's native usage tracking did not provide the necessary breakdown, showing only account-wide percentages and vague tags. Determined to gain detailed insights, the user developed a plugin called "quota-audit" to analyze the per-message token usage data stored in each local session under ~/.claude/projects/*/*.jsonl.

This plugin meticulously breaks down usage by project and skill, marking the exact moments when rate limits were breached and identifying the repositories that were throttled. The report generated by the plugin details financial estimates, highlighting which projects and skills dominate the usage, and even flags sessions that cross the 150,000 context threshold, which typically represent significant cost drivers.

It also helps identify any potential polling loops that may appear to inflate session counts without actually using quota. The user can access this tool within Claude Code either through the plugin marketplace or by running the claude plugin command. The report offers detailed insights into the quota consumption, but it's important to note that the dollar figures are estimates and not the actual bill, and the plugin can only view data from the machine it's running on, not from other devices or platforms.

The developer of the plugin, Rosehsu47, encourages users to explore how they can optimize their usage of Claude Code based on these valuable insights.