token-budgetlisted

Reduce token usage from large coding-agent context while preserving completion-critical evidence and full recoverability. Use when tool output, logs, diffs, test failures, search results, transcripts, or accumulated session context are large or repetitive; when context limits approach; or when the user asks to reduce tokens, compact context, lower agent cost, or preserve progress across compaction.
arjunkshah/token-skill · ★ 1 · Code & Development · score 74

Install: claude install-skill arjunkshah/token-skill

# Token Budget Minimize context, not evidence. ## Rules 1. Never compact the user's current request, acceptance criteria, active constraints, unresolved errors, or uncommitted-change warnings. 2. Keep exact commands, file paths, line references, failing test names, error messages, decisions, and latest task state. 3. Archive the full source before omitting content. Treat a capsule without a retrievable archive as lossy. 4. Prefer targeted reads (`rg`, line ranges, structured queries) over reading entire files. 5. Prefer summaries of successful output; preserve failure output verbatim. 6. Retrieve archived lines before acting when a capsule says evidence was omitted and the missing detail could affect correctness. 7. Do not reduce verification, skip tests, shorten required code, or stop early to save tokens. ## Compact large material Run the bundled CLI from the project root: ```bash python3 "${CLAUDE_SKILL_DIR:-$HOME/.codex/skills/token-budget}/scripts/tokenop.py" compact PATH ``` In Codex, resolve the installed skill path from the active skill metadata when `${CLAUDE_SKILL_DIR}` is unavailable. For stdin: ```bash COMMAND 2>&1 | python3 PATH_TO_SKILL/scripts/tokenop.py compact - ``` Use `--max-chars 8000` for routine output and increase it when critical evidence does not fit. Read the emitted capsule instead of the original bulk output. ## Work token-efficiently - Search first, then open only relevant ranges. - Run independent reads in parallel. - Do not re-read un