From token-optimizer
Open the Token Optimizer dashboard. Collects latest session data, regenerates the dashboard, and opens it in your browser.
How this skill is triggered — by the user, by Claude, or both
Slash command
/token-optimizer:token-dashboardThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Opens an up-to-date dashboard showing your context usage trends, quality scores, session history, and skill management.
Opens an up-to-date dashboard showing your context usage trends, quality scores, session history, and skill management.
RUNTIME="${TOKEN_OPTIMIZER_RUNTIME:-}"
if [ -z "$RUNTIME" ]; then
if [ -n "$CLAUDE_PLUGIN_ROOT" ] || [ -n "$CLAUDE_PLUGIN_DATA" ]; then
RUNTIME="claude"
elif [ -n "$CODEX_HOME" ] || [ -d "$HOME/.codex" ]; then
RUNTIME="codex"
else
RUNTIME="claude"
fi
fi
MEASURE_PY=""
for f in "$HOME/.codex/skills/token-optimizer/scripts/measure.py" \
"$HOME/.codex/plugins/cache"/*/token-optimizer/*/skills/token-optimizer/scripts/measure.py \
"$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. Is Token Optimizer installed?"; exit 1; }
export TOKEN_OPTIMIZER_RUNTIME="$RUNTIME"
python3 "$MEASURE_PY" collect --quiet && python3 "$MEASURE_PY" dashboard
This collects the latest session data into the trends database, regenerates the dashboard HTML, and opens it in your default browser.
python3 "$MEASURE_PY" daemon-status 2>/dev/nullURL: http://localhost:24842/token-optimizer (bookmarkable, auto-updates), then mention the file fallback.File: ~/.claude/_backups/token-optimizer/dashboard.html.File: ~/.codex/_backups/token-optimizer/dashboard.html.python3 $MEASURE_PY setup-daemon (macOS and Windows).npx claudepluginhub matrixy/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.
4plugins reuse this skill
First indexed Jul 10, 2026