What problem does it solve?
Context-budget helps you estimate the per-turn token usage caused by your project’s .claude/ configuration and CLAUDE.md, so you can avoid silent prompt bloat and understand what will load every turn versus only when invoked.
Core Features & Use Cases
- Always-loaded vs scoped vs invoked-only breakdown: Identifies which rules, skills, and agents contribute to every-turn context versus those that only load when paths match or when commands are triggered.
- Token estimation with two methods: Uses a chars/4 heuristic by default, or supports exact token counting via Anthropic’s count_tokens endpoint when --api is provided and an API key is available.
- Budget verdict and trimming guidance: Aggregates totals, ranks the top always-loaded contributors, flags overruns, and recommends the highest-leverage trim target.
Quick Start
Run the context-budget skill to generate a token-cost report for your current project’s .claude configuration and CLAUDE.md.