agentleFS
I-OnlabsI-Onlabs/claude-code-skills/token-optimization/SKILL.md

token-optimization

Skill4 starsChanged 29 days agoMITView on GitHub

Token-aware patterns for efficient context usage. Activates when working on long sessions, large codebases, or when context pressure is detected. Provides strategies for reducing token consumption while maintaining quality.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Avoid complex work at: >80% capacity

    line 22
  2. Distinctive:

    Instead of loading everything upfront:

    line 36
  3. Distinctive:

    Use efficient search patterns:

    line 43
  4. Distinctive:

    Only enable needed MCP servers per session

    line 76
  5. Very specific:

    Use claude mcp list to audit

    line 78
  6. Distinctive:

    Check decision-audit.jsonl for context

    line 98
  7. Distinctive:

    Work: Add context as needed

    line 144

“Common” is measured: kept by at least 6 in 10 of the 7 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

Token Optimization Skill

When This Skill Activates

This skill provides methodology for efficient token usage:

  • Long-running sessions approaching context limits
  • Large codebase exploration
  • Multiple file modifications
  • Complex multi-step tasks

Token Awareness

Context Budget

  • Total context: ~200K tokens
  • Practical limit: ~160K (leave buffer)
  • Compact at: 70% capacity
  • Avoid complex work at: >80% capacity

Token Costs (Approximate)

ContentTokens
1 line code~10-20
1 page text~500
Average file~500-2000
CLAUDE.md~3000
Full conversationGrows rapidly

Optimization Strategies

1. Progressive Disclosure

Instead of loading everything upfront:

Bad:  Read all 50 files at once
Good: Read index → identify relevant → read specific

2. Targeted Search

Use efficient search patterns:

Bad:  Read entire directory tree
Good: Glob pattern → Grep specific → Read matches

3. Minimal Context

Include only what's needed:

Bad:  Include entire file for small change
Good: Include function + surrounding context

4. Structured Summaries

For long outputs:

Bad:  Full test output (10K tokens)
Good: Summary + key failures (500 tokens)

5. Timely Compaction

Monitor and compact proactively:

Bad:  Wait for "Context low" warning
Good: Compact at 70% after task completion

MCP Token Management

Problem: MCP Server Token Drain

MCP tools can consume 30-60K tokens before conversation starts.

Solution: Selective Loading

  • Only enable needed MCP servers per session
  • Disable unused servers when not needed
  • Use claude mcp list to audit

Memory Server Strategy

ServerWhen to Use
memory-keeperSession continuity, compaction recovery
server-memoryLong-term key-value storage
NeitherShort, focused tasks

Compaction Strategy

Pre-Compaction Checklist

  1. ✅ Critical context saved to memory MCP
  2. ✅ Important decisions documented
  3. ✅ Current task state captured
  4. ✅ Key file paths noted

Post-Compaction Recovery

  1. Load context from memory MCP
  2. Re-read critical files if needed
  3. Check decision-audit.jsonl for context
  4. Resume task from documented state

Code Patterns

Efficient File Operations

# Bad: Read all then filter
for f in all_files:
    content = read(f)
    if "pattern" in content:
        process(f)

# Good: Search first then read
matches = grep("pattern", all_files)
for f in matches:
    content = read(f)
    process(f)

Efficient Updates

# Bad: Full file replacement
content = read(file)
new_content = content.replace(old, new)
write(file, new_content)

# Good: Targeted edit
edit(file, old_string=old, new_string=new)

Efficient Exploration

# Bad: Deep recursive exploration
explore_all_directories(root)

# Good: Breadth-first with limits
list_top_level(root)
identify_relevant_dirs()
explore_targeted(relevant_only)

Session Management

Long Session Strategy

  1. Start: Load minimal context
  2. Work: Add context as needed
  3. Checkpoint: Save state periodically
  4. Compact: At 70% or task completion
  5. Recover: Restore from checkpoint

Task Batching

Bad:  One massive continuous session
Good: Multiple focused sessions with clear handoffs

Integration with Hooks

Pre-Compact Hook

Automatically triggered when context low:

  • Backs up transcript
  • Creates recovery index
  • Logs compaction event

Session Start Hook

Restores context efficiently:

  • Loads minimal git status
  • Checks for recovery context
  • Provides continuation hints

Metrics to Monitor

Track these for optimization:

  • Session length before compaction
  • Files read per task
  • Tool calls per operation
  • Recovery success rate

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.