usage-limit-reducer
Usage Limit Reducer
Apply Dubi's 11 rules for cutting Claude token usage. Claude re-reads the entire conversation every turn, so 98.5% of tokens often go to re-reading history instead of generating responses. This skill diagnoses where the user's tokens are going and applies the rules that actually move the needle.
How to run this skill
Do the steps in order. Skip any step that clearly doesn't apply, but don't skip all of them — the value is in matching rules to what the user is actually doing.
Step 1 — Run the real token-usage report
Rule #4: "you can't fix what you can't measure." Claude Code already writes every token, model, and timestamp to ~/.claude/projects/<project>/<session>.jsonl. Run the bundled script to show the breakdown (use the absolute path to scripts/usage-report.py inside this skill's directory):
python3 <SKILL_DIR>/scripts/usage-report.py --days 7
Flags: --days N (default 7), --project <substring> to scope by cwd, --json for machine-readable output. Share the headline numbers with the user — cache-hit % and model mix are the two that matter most. A low cache-hit % (under ~60%) means too many fresh chats or cache-busting edits; high Opus share for routine work means Rule #8 applies.