Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/joseph27/claude-code-token-save/skillnpx skills add joseph27/claude-code-token-save --skill skillgit clone --depth 1 https://github.com/joseph27/claude-code-token-saveWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00061 | $0.00602 |
| Opus 5 | $0.00030 | $0.00301 |
| Sonnet 5 | $0.00012 | $0.00120 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
token-save scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Token-Save Mode
What to Do
- Read current state from
~/.claude/token-save-mode(if file doesn't exist, default isoff) - Read routing config from
~/.claude/token-save-routing.json - Determine action based on argument:
/token-save on→ set toon/token-save off→ set tooff/token-save(no arg) → toggle current state/token-save status→ show current state + routing summary, don't toggle/token-save routing→ show full routing table with all skills per tier
- Write new state to
~/.claude/token-save-mode(skip forstatus/routing) - Report the change to the user
Output Format
After toggling, read ~/.claude/token-save-routing.json and display:
Token-Save Mode: [ON/OFF]
[If ON:]
Model routing active (from ~/.claude/token-save-routing.json):
Opus (max quality) → [list skills from opus tier]
Sonnet (balanced) → [list skills from sonnet tier]
Haiku (cheapest) → [list skills from haiku tier]
Default for unlisted skills: [default_when_on value]
Enforcement: CLAUDE.md global rule applies to ALL Agent() calls.
[If OFF:]
All skills use Opus (default behavior). Maximum quality, maximum cost.
Routing Config Location
~/.claude/token-save-routing.json — this is the single source of truth for tier assignments.
Enforcement Layer
The enforcement lives in ~/.claude/CLAUDE.md under "Token-Save Mode (Agent Model Routing)". It instructs Claude to:
- Check
~/.claude/token-save-modebefore every Agent call - Look up the skill/task in the routing config
- Apply the tier's model, or
default_when_onif unlisted
Skills do NOT need their own token-save logic — the global CLAUDE.md rule handles it.
Moving a Skill Between Tiers
If the user asks to change a skill's tier (e.g., "move brainstorming to opus"), edit ~/.claude/token-save-routing.json directly:
- Remove the skill from its current tier's array
- Add it to the target tier's array
- Confirm the change
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 60 lines · 61 tokens per session scan A ddbe56f64bdf
token-save is a skill published in the GitHub repository joseph27/claude-code-token-save (2 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 602 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.