Borrowing it
Nothing to install: this file belongs to itsarmaanverma/local-token-saver. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/itsarmaanverma/local-token-saver/main/AGENTS.mdgit clone --depth 1 https://github.com/itsarmaanverma/local-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/itsarmaanverma/local-token-saver/agents-md)<a href="https://agentmods.dev/instructions/itsarmaanverma/local-token-saver/agents-md"><img src="https://agentmods.dev/badge/instructions/itsarmaanverma/local-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.00373 | $0.00373 |
| Opus 5 | $0.00187 | $0.00187 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
local-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 7d 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.
What it actually says
Codex Continuation Instructions
This repository uses agent-mesh for sequential continuity between Codex and Claude. Work on exactly one checklist task at a time.
Start every session
- Set
MESH_PLATFORM=codex. - Run
python C:/Users/armaa/agent-mesh/mesh.py resume --platform codex. - Read
docs/PHASE_PROGRESS.mdand the newest.agent-mesh/handoff.mdblock addressed tocodexorany. - Run
git status --short --branchand inspect existing changes before editing. - Continue only the active task, or claim the first unchecked task if none is active.
Editing and verification rules
- Coordination mode is sequential. Do not launch parallel agents or begin another checklist item.
- Claim the task and run
mesh checkfor every planned file before editing. - Keep code, tests, benchmarks, and documentation changes inside the current task's scope.
- Do not mark a task complete until targeted tests, the full suite, changed-file lint, and its benchmark pass.
- Baseline: 83 passed, 6 skipped, and one Windows containment failure. No phase may add failures; P02 must remove the known failure.
- Preserve unrelated changes and never rewrite shared history.
Complete or pause a task
- Cross off the task in
docs/PHASE_PROGRESS.md; add a brief summary, verification evidence, commit SHA, and two-line handoff. - Run
mesh done <task-id>, append a handoff toany, push the checkpoint, and stop. - Do not start the next task without explicit user approval.
- If blocked or close to a usage cutoff, leave the working tree intact, record dirty files and the next command, append a handoff, and stop.
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.
- 7d ago First seen · 29 lines · 373 tokens per session scan A f36585995bf8
local-token-saver AGENTS.md is an instructions file published in the GitHub repository itsarmaanverma/local-token-saver (2 stars, last pushed 1mo ago), licensed MIT. It adds 373 tokens to every session, about $0.0019 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.