context-budget

To optimize Claude Code context window token consumption, audit your setup to analyze token usage across loaded agents, skills, MCP servers, and rules. This process identifies bloated descriptions and redundant components, providing prioritized recommendations to reclaim context space.

Your Claude Code session runs out of context space quickly due to bloated component descriptions, heavy agents, redundant rules, and over-subscription issues. Running a context budget audit identifies these specific inefficiencies and recommends actions to save tokens for future additions.

The best way to audit token usage across Claude Code agents and skills is to perform a dedicated context budget analysis. This classifies all loaded components, detects redundancies, and offers prioritized optimization recommendations to reduce token consumption.

Yes, you can analyze MCP servers and rules for token optimization in Claude Code. A context budget audit applies to agents, skills, MCP servers, and rules, scanning each component to identify inefficiencies and recommend actions to save context space.

You need to perform a context budget audit when you have added numerous skills, agents, and rules to your Claude Code setup. Auditing helps manage token consumption by identifying over-subscription issues and reclaiming context space for future component additions.