Skip to content
Back to skills

Context Budget

ASecurity

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.

  • 434 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
ai-agentsperformance

Works with

  • cursor
  • cli
  • mcp

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add coco-research/coco --skill context-budget --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Context Budget?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Context Budget
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/coco-research-context-budget/badge)](https://www.skillsdirectory.com/skills/coco-research-context-budget)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: context-budget
description: "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."
domain: meta
supports: [claude-code, cursor, codex, generic, windsurf, zed, cline, roo-code, amazon-q]
version: 0.1.0
tags: [context, tokens, optimization, audit]
---

@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-budget` command (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 `description` frontmatter 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:ship` to verify context headroom
- Feed results to learning system as optimization instincts
- Cross-reference with Brain DB decisions about past context issues

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…