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 instructions/supersynergy/agent-token-saver/agents-mdgit clone --depth 1 https://github.com/Supersynergy/agent-token-saverWrote 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/instructions/supersynergy/agent-token-saver/agents-md)<a href="https://agentmods.dev/instructions/supersynergy/agent-token-saver/agents-md"><img src="https://agentmods.dev/badge/instructions/supersynergy/agent-token-saver/agents-md.svg" alt="Measured on agentmods" 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.00464 | $0.00464 |
| Opus 5 | $0.00232 | $0.00232 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
agent-token-saver AGENTS.md 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 yesterday.
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.
What it actually says
Agent Token Saver
Portable context reduction. Hooks stay fail-open; optional tools stay optional.
Commands
- setup:
uv sync --extra dev - test:
uv run pytest -q - lint:
uv run ruff check scripts integration tests - smoke:
bash scripts/neutral_install_smoke.sh - live install check:
agent-token-saver doctor --profile teams --json
Rules
- Preserve user changes. No destructive Git.
- Smallest change. Tests for behavior. ADR for durable design decisions.
- Public files: no private paths, credentials, PIDs, transcripts or host-only claims.
- Portable core first. Third-party CLIs are detected, never silently installed.
- Hook code receives JSON, returns JSON or nothing, and never changes approval, sandbox or stop ownership.
- No maintenance scan in a hook.
synx doctoris manual-only. - One controller; workers get one capsule, one oracle, zero or one skill and a compact evidence result. Three independent workers maximum by default.
Product boundary
minimal: CLI/ledger only.lean: compact host default, prompt gate, session guard and optional routing/projection CLIs.teams: Lean plus Claude's worker-capsule hook; no automatic fan-out.heavy: opt-in graph/large-context tools for one session.
Codex and Claude use merged JSON hooks plus compact global defaults. Hermes
uses a managed block in an existing SOUL.md; GG Coder uses the home
AGENTS.md; both retain installed skills for explicit full loading. Verify
active configuration with the doctor; files on disk are not proof.
References
- README: install and user-facing contract.
- playbook: phase-by-phase usage path and version drift.
- hooks: host matrix.
- tooling: default versus optional layers.
- measurement: method and limits.
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.
- yesterday Changed · +1 lines · +20 tokens per session 363022689330
- 6d ago First seen · 46 lines · 444 tokens per session scan A d4afb922e650
agent-token-saver AGENTS.md is an instructions file published in the GitHub repository Supersynergy/agent-token-saver (7 stars, last pushed yesterday), licensed MIT. It adds 464 tokens to every session, about $0.0023 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 instructions, from other repositories
aeon CLAUDE.md
Claude Code instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
cognirepo CLAUDE.md
Claude Code instructions for ashlesh-t/cognirepo, covering claude.md, key rules, session start sequence (run in this order), behavioral confirmation rule and personas (cognirepo-402, cognirepo-403).
wayland-core copilot-instructions.md
Copilot instructions for FerroxLabs/wayland-core, covering ijfw rules, output discipline, memory routing, context discipline and cross-audit.
mcp-structured-memory CLAUDE.md
Claude Code instructions for nmeierpolys/mcp-structured-memory, a project described as: Structured Memory MCP Server.
inkwell-memory CLAUDE.md
Instructions for veronchenko/inkwell-memory, covering claude.md — inkwellmemory, layout, multi-tenant mode (inkwellmultitenant=1), conventions and testing.
RNR-Enhanced-Cognee AGENTS.md
AGENTS.md instructions for vincentspereira/RNR-Enhanced-Cognee, covering rnr enhanced cognee implementation for codex, critical requirements, 1. ascii-only output (no unicode encoding), 2. dynamic categories (no hardcoded categories) and 3. standard memory mcp interface.