What problem does it solve? Claude Code sessions accumulate hidden token overhead from agents, skills, MCP servers, rules, and CLAUDE.md files, degrading performance and shrinking usable context without any visibility into where the budget went. ## Core Features & Use Cases - Component Inventory: Scans agents, skills, rules, MCP servers, and CLAUDE.md files, estimating token consumption per component with heuristics like words × 1.3 and ~500 tokens per MCP tool schema. - Issue Detection: Flags bloated agent descriptions, heavy files, redundant components, MCP over-subscription, and CLAUDE.md bloat, then classifies each component as always, sometimes, or rarely needed. - Prioritized Report: Produces a context budget report with per-component token breakdowns and ranked optimizations, plus a verbose mode with per-file and per-tool detail. - Use Case: Before adding five new MCP servers, run the audit to learn current overhead is 33% and that removing two CLI-replaceable servers first keeps you under a 40% overhead target. ## Quick Start Ask the assistant to run a context budget audit of the current Claude Code setup and report the top token-saving optimizations.