context-budget
SkillAI & modelsAudits how many tokens your agent's loaded components consume and recommends what to trim to free context space.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the context-budget skill
About this capability
Audit token consumption across agents, skills, MCP servers, and rules. Identifies bloat, redundant components, and produces prioritized token-savings recommendations. Use when the context window is filling up too fast or before adding new components.
What this skill tells your AI
The instructions your AI receives, as published by coco-research/coco in skills/context-budget/SKILL.md and read by ahel’s review.
@agents/PROMPT-DEFENSE.md
Context Budget Audit
Analyze token overhead across every loaded component in a session and surface actionable optimizations to reclaim context space.
When to Use
- Session performance feels sluggish or output quality is degrading
- You've recently added many skills, agents, or MCP servers
- Planning to add more components and need to know if there's room
- Running
/context-budgetcommand (this skill backs it)
Audit Procedure
Phase 1: Inventory
Scan all component directories and estimate token consumption:
Agents (agents/*.md)
- Count lines and tokens per file (words × 1.3)
- Extract
descriptionfrontmatter length - Flag: files >200 lines (heavy), description >30 words (bloated frontmatter)
Skills (skills/*/SKILL.md)
- Count tokens per SKILL.md
- Flag: files >400 lines
- Check for duplicate copies — skip identical copies to avoid double-counting
Rules (rules/**/*.md, rules/**/*.mdc)
- Count tokens per file
- Flag: files >100 lines
- Detect content overlap between rule files
MCP Servers (active MCP config)
- Count configured servers and total tool count
- Estimate schema overhead at ~500 tokens per tool
- Flag: servers with >20 tools
CLAUDE.md / System Prompts
- Count tokens in CLAUDE.md chain
- Flag: combined total >300 lines
Phase 2: Classify
Sort every component into a bucket:
| Bucket | Criteria | Action |
|---|---|---|
| Always needed | Referenced in CLAUDE.md, backs active command, matches project type | Keep |
| Sometimes needed | Domain-specific, not referenced in CLAUDE.md | Consider on-demand activation |
| Rarely needed | No command reference, overlapping content, no project match | Remove or lazy-load |
Phase 3: Report
Generate a prioritized savings report:
CONTEXT BUDGET AUDIT
====================
Total estimated tokens: {total}
Context headroom: {headroom}%
TOP SAVINGS OPPORTUNITIES:
1. {component} — {tokens} tokens ({bucket}) → {recommendation}
2. {component} — {tokens} tokens ({bucket}) → {recommendation}
...
ALWAYS NEEDED (keep):
- {component} ({tokens} tokens)
SOMETIMES NEEDED (lazy-load candidates):
- {component} ({tokens} tokens)
RARELY NEEDED (removal candidates):
- {component} ({tokens} tokens)
Token Estimation Formula
- English text: ~1.3 tokens per word
- Code: ~1.5 tokens per word (more punctuation/symbols)
- YAML frontmatter: ~1.2 tokens per word
- MCP tool schema: ~500 tokens per tool definition
Integration Points
- Run automatically before
/team:shipto verify context headroom - Feed results to learning system as optimization instincts
- Cross-reference with Brain DB decisions about past context issues
Signals
- GitHub stars
- 320
- Forks
- 12
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
context-budget-coco-research- Source
- github.com/coco-research/coco