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/webcoyote/sandvault/agents-mdgit clone --depth 1 https://github.com/webcoyote/sandvaultWrote 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/webcoyote/sandvault/agents-md)<a href="https://agentmods.dev/instructions/webcoyote/sandvault/agents-md"><img src="https://agentmods.dev/badge/instructions/webcoyote/sandvault/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 | $0.00037 | $0.00037 |
| Opus 5 | $0.00018 | $0.00018 |
| Sonnet 5 | $0.00007 | $0.00007 |
| Haiku 4.5 | $0.00004 | $0.00004 |
Grade A, and why
sandvault 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 3d 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
AGENTS.md
Testing
When making changes always run ./scripts/validate before responding. Report it's results in your response. If you could not run them, explain why.
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.
- 3d ago First seen · 7 lines · 37 tokens per session scan A f119e25c4926
sandvault AGENTS.md is an instructions file published in the GitHub repository webcoyote/sandvault (393 stars, last pushed 4d ago), licensed Apache-2.0. It adds 37 tokens to every session, about $0.0002 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-30.
Other instructions, from other repositories
microsandbox AGENTS.md
AGENTS.md instructions for superradcompany/microsandbox, covering agents.md, scope, project map, design principles and backward compatibility review.
agent-safehouse AGENTS.md
AGENTS.md instructions for eugene1g/agent-safehouse, covering agent safehouse: llm quick reference, what this project is, fast working rules, core commands and generate policy only (prints temp policy path).
greywall CLAUDE.md
Instructions for GreyhavenHQ/greywall, covering greywall, build & run, test, lint & format and project structure.
agent-deck AGENTS.md
Instructions for breakstring/agent-deck, covering agents.md, 项目定位, 必读文档, 工作流 and 当前代码结构.
codex-project-skill-manager AGENTS.md
Instructions for WildPigKing/codex-project-skill-manager, covering codex project & skill manager, product boundary, startup routing, consent contract and repository records.
codex-token-meter AGENTS.md
Instructions for prefect12/codex-token-meter, covering ai token meter development guide, project shape, build and verification, git workflow and ai token meter test loop.