What problem does it solve?
Tracking Claude Code token consumption across multiple projects and sessions is tedious and time-consuming, making it hard to identify costly usage patterns, optimize AI spending, and spot unexpectedly expensive subagent runs.
Core Features & Use Cases
- Cross-project usage tracking: Scans all local Claude Code session files to generate a full breakdown of token usage per project, including input, cache creation, cache read, and output tokens.
- Costliest session identification: Highlights the top 25 most token-heavy sessions with their first prompts, so you can quickly pinpoint what drove high usage.
- Subagent usage analysis: Breaks down token consumption by subagent to ensure specialized AI runs are proportional to their value.
- Use Case: If you run multiple client projects in Claude Code, use this skill to generate a report that shows which project is using the most tokens, if any subagent runs are driving up costs, and which sessions were the most expensive.
Quick Start
Ask Claude to run the token-usage skill to generate a full markdown report of your Claude Code token usage across all projects and sessions, filtered to your desired time range.