context-budget

Auditing token consumption involves inventorying all active agents, skills, MCP servers, and rules to classify usage and detect bloated descriptions or over-subscriptions. This generates a structured report with prioritized mitigations to reduce context overhead.

Token waste typically stems from redundant components, bloated descriptions, and MCP over-subscription. When managing complex tasks, unnecessary context overhead accumulates across active rules, requiring a classification audit to identify and prune non-essential elements.

To optimize token footprint, run an audit to inventory components and classify them by necessity. This detects bloated descriptions and redundant rules, producing an actionable plan to prune token-hogging components and streamline context overhead.

Yes, MCP over-subscription is detected by auditing token usage across servers and agents. The audit classifies components by necessity, identifies excessive subscriptions, and provides recommendations to reduce unnecessary context overhead.

The best way to generate a prioritized optimization plan is to audit token consumption and classify components by necessity. This detects issues like bloated descriptions and redundant rules, yielding a structured report with actionable mitigations.

You should run a token-usage audit during periodic maintenance or when managing complex tasks with many installed skills. It inventories components, detects redundant rules and MCP over-subscriptions, and recommends mitigations to cut token waste.