token-audit

You can audit fixed-context tokens by running this skill to measure token usage across global ~/.claude settings, project CLAUDE.md files, rules, and system prompts. It generates a prioritized action plan with estimated token savings for oversized inputs.

Fixed-context token overhead is the persistent token volume consumed by global settings, project CLAUDE.md files, memory, and system prompts. Auditing this overhead identifies oversized inputs and quantifies their impact on available context capacity.

To reduce token usage, run an audit to measure tokens loaded from your project CLAUDE.md and rules. The tool outputs a prioritized optimization plan with estimated savings and suggested changes to streamline your configuration.

Yes, the token audit is specifically designed for projects with large configs, numerous rules, and long system prompts. It quantifies token usage across these fixed-context sources and provides a prioritized action plan to optimize them.

Yes, the audit provides a repeatable workflow to quantify token impact before and after configuration changes. This allows you to measure fixed-context token reduction across diverse projects and verify your optimization results.