context-budget

Run a context budget audit to scan all loaded components, estimate token overhead, and flag heavy items. It categorizes components by necessity and generates a report with actionable savings to reclaim context window headroom.

Reducing token overhead from MCP servers and skills requires identifying bloated descriptions, redundant components, and MCP over-subscription. A context budget audit detects these issues and prioritizes optimizations to improve session performance.

Yes, you can check context window headroom before deployment by running a context budget audit. It inventories all active agents, skills, rules, and CLAUDE.md files, classifying their token impact to ensure there is enough space.

A context budget report classifies loaded components into Always needed, Sometimes needed, or Rarely needed categories. This classification, combined with per-file heuristics, helps assess impact and prioritize token savings across agents and MCP servers.

A Claude Code session runs out of context window space when accumulated token overhead from agents, skills, rules, and CLAUDE.md exceeds limits. Auditing identifies bloated descriptions and redundant components to reclaim token headroom.

Yes, the context budget audit works with custom CLAUDE.md files and rules. It applies token-estimation rules and per-file heuristics across every loaded component to identify headroom, assess impact, and prioritize savings.