agentleFS
LucfaceLucface/claude-skills/skills/context-budget/SKILL.md

context-budget

Skill1 starsChanged 3 days agoMITView on GitHub

Audit token consumption across all loaded components — skills, agents, MCP tools, rules, hooks

60 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-payment-x402, openclaw-persona-forge and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • TironFoxSkill

    agent-payment-x402

    Add x402 payment execution to AI agents — per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents need to pay for APIs, services, or other agents.

    Also in 6 projects that use this

  • TironFoxSkill

    openclaw-persona-forge

    为 OpenClaw AI Agent 锻造完整的龙虾灵魂方案。根据用户偏好或随机抽卡, 输出身份定位、灵魂描述(SOUL.md)、角色化底线规则、名字和头像生图提示词。 如当前环境提供已审核的生图 skill,可自动生成统一风格头像图片。 当用户需要创建、设计或定制 OpenClaw 龙虾灵魂时使用。 不适用于:微调已有 SOUL.md、非 OpenClaw 平台的角色设计、纯工具型无性格 Agent。 触发词:龙虾灵魂、虾魂、OpenClaw 灵魂、养虾灵魂、龙虾角色、龙虾定位、 龙虾剧本杀角色、龙虾游戏角色、龙虾 NPC、龙虾性格、龙虾背景故事、 lobster soul、lobster character、抽卡、随机龙虾、龙虾 SOUL、gacha。

    Also in 5 projects that use this

  • loulanyueSkill

    nuxt4-patterns

    Nuxt 4 app patterns for hydration safety, performance, route rules, lazy loading, and SSR-safe data fetching with useFetch and useAsyncData.

    Also in 9 projects that use this

  • renepfSkill

    orch-pipeline

    Shared orchestration engine for the orch-* skill family. Defines the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates that the orch-* operation skills delegate to. Not usually invoked directly.

    Also in 4 projects that use this

  • Exploration-labsSkill

    token-budget-advisor

    Proactive token budget assessment and task chunking strategy. Use this skill when queries involve multiple large file uploads, requests for comprehensive multi-document analysis, complex multi-step workflows with heavy research (10+ tool calls), phrases like "complete analysis", "full audit", "thorough review", "deep dive", or tasks combining extensive research with large output artifacts. This skill helps assess token consumption risk early and recommend chunking strategies before beginning work.

    Also in 11 projects that use this

  • loulanyueSkill

    santa-method

    Multi-agent adversarial verification with convergence loop. Two independent review agents must both pass before output ships.

    Also in 8 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 55 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run these in parallel:

    line 19
  2. Distinctive:

    Keep MCP servers under 10 enabled / under 80 total tools

    line 69
  3. Distinctive:

    Consider disabling MCP servers you use < once/week

    line 71
  4. Distinctive:

    Check if any plugins overlap in functionality

    line 72

“Common” is measured: kept by at least 6 in 10 of the 55 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Context Budget Audit

Estimate how much of your context window is consumed by the agent harness infrastructure vs actual work.

When to Use

  • Context feels heavy or compacting frequently
  • Adding new skills/MCPs and want to know the cost
  • Optimizing which components stay loaded

Process

1. Inventory All Loaded Components

Run these in parallel:

Enabled plugins (each can add MCP tools):

# Count enabled plugins; each MCP tool a plugin adds costs ≈ 500 tokens of schema
cat ~/.claude/settings.json | python3 -c "
import json, sys
d = json.load(sys.stdin)
# Count enabled plugins
plugins = {k:v for k,v in d.get('enabledPlugins',{}).items() if v}
print(f'Enabled plugins (MCP tools not counted): {len(plugins)}')
for p in plugins: print(f'  - {p}')
"

Installed skills: Count ~/.claude/skills/*/SKILL.md plus the project's .claude/skills/*/SKILL.md:

find -L ~/.claude/skills .claude/skills -mindepth 2 -maxdepth 2 -name SKILL.md 2>/dev/null | wc -l

Each skill listing in the system prompt ≈ 100-200 tokens.

Agent definitions: Each agent defined in ~/.claude/agents/ ≈ 300-800 tokens when loaded.

Hook definitions: Each hook in settings.json ≈ 50-100 tokens.

2. Estimate Token Budget

ComponentPer-Unit EstimateCountTotal
MCP tool schema~500 tokens??
Skill listing (system prompt)~150 tokens??
Agent definition~500 tokens??
Hook definition~75 tokens??
CLAUDE.mdmeasure directly1?
MEMORY.mdmeasure directly1?

Key insight from everything-claude-code (Affaan Mustafa): "Your 200k context window before compacting might only be 70k with too many tools enabled."

3. Classify Components

For each component, classify:

  • Always: Core workflow, used every session
  • Sometimes: Domain-specific, used in certain projects
  • Rarely: Niche, could be loaded on-demand

4. Recommendations

  • Keep MCP servers under 10 enabled / under 80 total tools
  • Move "Rarely" skills to on-demand invocation
  • Consider disabling MCP servers you use < once/week
  • Check if any plugins overlap in functionality

Output Format

CONTEXT BUDGET AUDIT: {date}
═══════════════════════════════
Estimated infrastructure overhead: ~{N}k tokens
Estimated available for work: ~{M}k tokens ({P}% of 200k)

TOP CONSUMERS:
1. {component}: ~{N} tokens
2. {component}: ~{N} tokens
...

RECOMMENDATIONS:
- {action}

Source

Inspired by Affaan Mustafa's everything-claude-code (https://github.com/affaan-m/everything-claude-code).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.