token-saverlisted
Install: claude install-skill Tomo214/token-diet
# Token Saver
Everything in context is re-sent on every later turn — the cheapest token is the one never loaded.
Priority: **correctness > quality > security > efficiency > tokens.** Before each step: does it move the result forward or make it safer? No → skip it.
## 1. Size the task (internally, before the first tool call)
- **Done-criterion:** one checkable sentence ("test X passes", "button centred on mobile").
- **Minimal path:** the files/spots that must change — read only those.
- **Smallest reliable check** that proves the criterion.
| Tier | Typical | Read | Tests | Subagents |
|---|---|---|---|---|
| A trivial | typo, one config value | target spot, 1–3 tool calls | check the change directly | never |
| B simple | small style fix, one function | + direct callers | 1 targeted check | never |
| C normal | feature, API integration, related files | affected files | affected tests | broad search only |
| D complex | hard bug, larger refactor | + dependencies | affected + adjacent | if real benefit |
| E very complex | architecture, system issue | + side effects | full relevant suite | second opinion OK |
Data loss, security, auth, payments, production, migrations, irreversible actions → at least +1 tier.
## 2. Reuse before fetching
- Already in context (file, output, answer) → use it. Don't re-read, re-run or re-ask.
- Resuming / long task: `git status -s`, `git log --oneline -10`, `git diff --stat` show what's done. Build on existing code and commits; never redo f