Skill detail

token-optimizer

Directly audits and reduces token/context waste with measurable savings.

MatchDirectReviewed for token optimization
Sourcealexgreensh/token-optimizerExternal source
Reported installs581Popularity signal only

Inspect before use

Automated review checks relevance, not safety or endorsement. Read the source instructions before using this skill.

Saved source preview

SKILL.md

The saved excerpt is a snapshot from review. The external source remains the complete and most current version.

---
name: token-optimizer
description: Audit a Claude Code or Codex setup for context-window waste, then fix it and measure the savings. Use when context feels tight.
effort: high
---

# Token Optimizer

> **Never recommend cutting our own tools (issue #111).** In every recommendation you produce, NEVER suggest removing, archiving, trimming, disabling, or consolidating Token Optimizer's own skills — `token-optimizer`, `token-coach`, `token-dashboard`, `fleet-auditor`. They are the measurement layer; recommending the user delete them to "save ~200 tokens" is self-cannibalizing. Exclude them from every unused-skill / archive / consolidation suggestion, regardless of invocation history.

Audits 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.

---

## Step 0: Resolve measure.py, then gate on runtime (run this first)

> **Runtime pre-gate (environment only — touches no `~/.claude` path).** Before resolving any script
> path, check the environment directly. This keeps non-Claude runtimes from ever resolving a
> `~/.claude` path (issue #57):
> ```bash
> # OpenCode / Copilot set these; detect them WITHOUT touching ~/.claude.
> # Explicit TOKEN_OPTIMIZER_RUNTIME is authoritative and checked first (matches detect_runtime()).
> # An explicit override to a Claude/Codex runtime is authoritative (matches detect_runtime); proceed.
> # Claude plugin env vars (CLAUDE_PLUGIN_ROOT/CLAUDE_PLUGIN_DATA) are checked BEFORE
> # OPENCODE_* env signals so a genuine Claude session with a stray OPENCODE_* export
> # is NOT stopped here — it falls through to measure.py, which resolves correctly
> # (detect_runtime step 3 beats step 4). This mirrors the Python priority order.
> if [ "${TOKEN_OPTIMIZER_RUNTIME:-}" = "claude" ] || [ "${TOKEN_OPTIMIZER_RUNTIME:-}" = "codex" ]; then
>   :  # fall through to the measure.py resolver + authoritative gate below
> elif [ "${TOKEN_OPTIMIZER_RUNTIME:-}" = "opencode" ]; then
>   echo "Token Optimizer — OpenCode runtime detected."
> elif [ "${TOKEN_OPTIMIZER_RUNTIME:-}" = "copilot" ]; then
>   echo "Token Optimizer — GitHub Copilot runtime detected."
> elif [ -n "${CLAUDE_PLUGIN_ROOT:-}${CLAUDE_PLUGIN_DATA:-}" ]; then
>   :  # genuine Claude Code session; fall through to measure.py (step 3 beats step 4)
> elif [ -n "${OPENCODE_BIN:-}${OPENCODE_CONFIG_DIR:-}${OPENCODE_DATA_DIR:-}${OPENCODE_CONFIG:-}${OPENCODE_CLIENT:-}" ]; then
>   echo "Token Optimizer — OpenCode runtime detected."
> elif [ -n "${COPILOT_HOME:-}${TOKEN_OPTIMIZER_COPILOT_HOME:-}" ]; then
>   echo "Token Optimizer — GitHub Copilot runtime detected."
> fi
> ```
> - Prints **"… OpenCode runtime detected."** → **STOP. Do not resolve `measure.py`, do not run any
>   phase below.** Read `references/opencode-workflow.md` (bundled with this skill) and follow it.
>   On OpenCode, Token Optimizer runs as a native plugin; the Claude audit must not run.
> - Prints **"… GitHub Copilot runtime detected."** → **STOP** and follow the Copilot guidance for the
>   same reason.
> - Prints nothing → continue to resolve `$MEASURE_PY` below. This env-only pre-gate does NOT
>   check the process tree, so OpenCode launched without exporting `OPENCODE_*` env vars (e.g. a
>   bare `opencode` binary or `node /path/to/opencode`) prints nothing here. The
>   `measure.py report` runtime gate that follows is the **authoritative** second check — it runs
>   `detect_runtime()` which includes the ancestor-process scan and will catch those cases.

Resolve the script path **once, before any phase or runtime decision**. Every
command below — including the runtime gate — depends on `$MEASURE_PY`, so it
must be set first:
```bash
# Resolve measure.py to the NEWEST installed copy across channels so a stale
# plugin-cache copy never shadows a fresh install (issue #57). find -L follows the
# install.sh symlink under ~/.claude/skills; cd -P re
Read the full source on GitHub (opens external page)
Context

Related work