From token-optimizer
Find the ghost tokens. Audit Claude Code or Codex setup, see where context goes, fix it. Use when context feels tight.
How this skill is triggered — by the user, by Claude, or both
Slash command
/token-optimizer:token-optimizerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Audits a Claude Code or Codex setup, identifies context window waste, implements fixes, and measures savings.
assets/before-after.svgassets/dashboard-overview.pngassets/dashboard.htmlassets/fleet-demo.htmlassets/hero-terminal.svgassets/how-it-works.svgassets/logo.svgassets/logo.txtassets/quality-example.svgassets/real-savings.svgassets/status-bar.svgassets/user-profiles.svgassets/v5-bash-compression.svgassets/v5-delta-mode.svgassets/v5-hero.svgassets/v5-nudges-loops.svgexamples/claude-md-optimized.mdexamples/hooks-starter.jsonexamples/permissions-deny-template.jsonreferences/agent-prompts.mdAudits a Claude Code or Codex setup, identifies context window waste, implements fixes, and measures savings.
Target: 5-15% context recovery through config cleanup, up to 25%+ with autocompact management.
If TOKEN_OPTIMIZER_RUNTIME=codex or Codex environment is detected, read references/codex-workflow.md and follow its chat-first workflow instead of the Claude Code phases below.
Resolve measure.py path:
MEASURE_PY=""
for f in "$HOME/.claude/skills/token-optimizer/scripts/measure.py" \
"$HOME/.claude/plugins/cache"/*/token-optimizer/*/skills/token-optimizer/scripts/measure.py; do
[ -f "$f" ] && MEASURE_PY="$f" && break
done
[ -z "$MEASURE_PY" ] && { echo "[Error] measure.py not found."; exit 1; }
Read references/phase0-setup.md for the full setup sequence: context window detection, pre-check, backup, coordination folder, hook checks, daemon setup, and smart compaction.
Read references/agent-prompts.md for all prompt templates.
Dispatch 6 agents in parallel:
| Agent | Output File | Model | Task |
|---|---|---|---|
| CLAUDE.md Auditor | audit/claudemd.md | sonnet | Size, duplication, tiered content, cache structure |
| MEMORY.md Auditor | audit/memorymd.md | sonnet | Size, overlap with CLAUDE.md |
| Skills Auditor | audit/skills.md | sonnet | Count, frontmatter overhead, duplicates |
| MCP Auditor | audit/mcp.md | sonnet | Deferred tools, broken/unused servers |
| Commands Auditor | audit/commands.md | haiku | Count, menu overhead |
| Settings & Advanced | audit/advanced.md | sonnet | Hooks, rules, settings, @imports, caching |
Pass COORD_PATH to each. Wait for all to complete. If any output file is missing, note the gap and proceed.
Read the Synthesis Agent prompt from references/agent-prompts.md. Dispatch with model="opus" (fallback: sonnet). It reads all audit files and writes {COORD_PATH}/analysis/optimization-plan.md. If missing, present raw audit files instead.
Read references/presentation-workflow.md for the findings template, dashboard generation, and URL presentation logic. Generate the dashboard:
python3 $MEASURE_PY dashboard --coord-path $COORD_PATH
Wait for user decision before proceeding.
Read references/implementation-playbook.md for detailed steps. Available actions: 4A-4P covering CLAUDE.md, MEMORY.md, Skills, File Exclusion, MCP, Hooks, Cache, Rules, Settings, Descriptions, Compact Instructions, Model Routing, Smart Compaction, Quality Check, Version-Aware Optimizations, and Smart Routing. Templates in examples/. Always backup before changes. Present diffs for approval.
Read the Verification Agent prompt from references/agent-prompts.md. Dispatch with model="haiku". Re-measures everything and calculates savings. Present before/after comparison and behavioral next steps.
| Context | Read |
|---|---|
| Codex runtime | references/codex-workflow.md |
| Phase 0 setup details | references/phase0-setup.md |
| Phase 1-2 agent prompts | references/agent-prompts.md, references/token-flow-architecture.md |
| Phase 3 presentation | references/presentation-workflow.md |
| Phase 4 implementation | references/implementation-playbook.md, examples/ |
| CLI commands | references/cli-reference.md |
| Phase 3 checklist | references/optimization-checklist.md |
| Error handling | references/error-recovery.md |
npx claudepluginhub toininoi/token-optimizerGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.