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 skills add Redclawww/savethetokens --skill savethetokensgit clone --depth 1 https://github.com/Redclawww/savethetokensWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/redclawww/savethetokens/savethetokens)<a href="https://agentmods.dev/skills/redclawww/savethetokens/savethetokens"><img src="https://agentmods.dev/badge/skills/redclawww/savethetokens/savethetokens/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/redclawww/savethetokens/savethetokens"><img src="https://agentmods.dev/badge/skills/redclawww/savethetokens/savethetokens.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00069 | $0.02304 |
| Opus 5 | $0.00034 | $0.01152 |
| Sonnet 5 | $0.00014 | $0.00461 |
| Haiku 4.5 | $0.00007 | $0.00230 |
Grade A, and why
savethetokens 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 12d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Governor
Optimize context usage with practical, high-impact workflows and scripts.
Non-Negotiable Guardrails
- Keep scope locked to the user request. Do not add extra features, pages, or telemetry unless asked.
- Treat token optimization as a constraint, not the goal. Correctness and security win over token reduction.
- Never claim token savings without before/after measurement on comparable tasks.
- If context-saving actions risk quality loss, keep the extra context and state the tradeoff.
- Never reduce code thoroughness to save tokens. Tests, strict config, safety checks, and error handling are non-negotiable. Save tokens from message verbosity — never from output completeness.
Operating Modes
Lean Mode(default): Use lightweight context hygiene only; do not create new benchmark artifacts.Measurement Mode: Use launch-readiness or A/B telemetry scripts only when user asks for proof/percentages.
Claude Code Message Budget (required)
- Keep progress updates short and phase-based. Do not narrate every file write.
- Do not paste long command output unless user asks. Summarize only key signals.
- Do not repeat the same command without a code/input change; if retried, state the reason once.
- If
/contextshows message growth is unusually high, switch to stricter concise mode:- fewer updates
- shorter summaries
- batch related edits before reporting
- Prefer one concise final summary over long running commentary.
- For benchmark runs, enforce matched behavior on both variants:
- same stop criteria
- same compact policy
- same output style (no extra giant report in one variant only)
Operating Playbook
- Confirm objective and lock scope in one sentence.
- Keep one chat session per task. Start a new session for unrelated work.
- Use
! <command>for direct shell commands when no reasoning is required. - Run
/contextperiodically. Compact around 50% usage instead of waiting for hard limits. - Before
/compactor/clear, create a checkpoint file with next steps and touched files. - Keep top-level docs lean; move deep details to linked
docs/*.md. - Before final output on code tasks, run the quality gates in
docs/QUALITY_GATES.md. - For token-savings claims, run matched A/B using
docs/BENCHMARK_PROTOCOL.md. - For Claude benchmark runs, use
docs/STRICT_BENCHMARK_PROMPT.mdas the session starter.
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.
- 12d ago First seen · 201 lines · 69 tokens per session scan A 51bf6487d586
savethetokens is a skill published in the GitHub repository Redclawww/savethetokens (10 stars, last pushed 7mo ago), licensed MIT. It adds 69 tokens to every session and 2,304 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…