context-budget

Session latency and accuracy drops often stem from context bloat. Auditing your Claude Code context budget reveals token-heavy or redundant components, such as verbose agent descriptions and overlapping rules, that drain usable capacity.

You can audit context consumption by generating a staged inventory that scans your agents, skills, rules, MCP servers, and CLAUDE.md references. This process categorizes loaded components and detects issues to estimate token load.

The best way to reduce MCP tool token bloat is to run an audit that flags heavy configurations and recommends removals or delayed activation. This optimization plan helps recover effective usable context capacity.

Yes, you can get an optional verbose file-level breakdown of token usage. The audit produces a prioritized context budget report that includes estimated token savings and highlights top opportunities across your components.

You should run a context budget audit during ongoing development when adding or activating multiple components. It is specifically designed to apply when session latency increases or output quality drops.

Yes, context budgeting works without external dependencies. It functions by scanning your existing Claude Code configuration files and component definitions to identify redundancy and estimate token savings natively.