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/fantasyce/agent-recall-trail/agents-mdgit clone --depth 1 https://github.com/fantasyce/agent-recall-trailWrote 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/fantasyce/agent-recall-trail/agents-md)<a href="https://agentmods.dev/instructions/fantasyce/agent-recall-trail/agents-md"><img src="https://agentmods.dev/badge/instructions/fantasyce/agent-recall-trail/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.00181 | $0.00181 |
| Opus 5 | $0.00090 | $0.00090 |
| Sonnet 5 | $0.00036 | $0.00036 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
agent-recall-trail 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
ART development contract
- The current design and implementation plans under
docs/specs/anddocs/plans/are the product and acceptance contracts. - Use test-driven development. Observe each new behavior test fail before implementing it.
- Keep every Agent Vault in a physically distinct SQLite file and bind MCP identity at process start.
- Memory and published knowledge are different object families. Agents never approve or publish knowledge.
- Do not read, copy, translate, or structurally imitate competitor source code, schemas, prompts, tests, names, or directory layouts.
- Tests use an explicit task-owned
ART_HOME; never write test data to the formal~/.acrossruntime. - Do not modify unrelated products, existing knowledge sources, or formal Codex/DSH configuration during automated tests.
- Do not persist secrets, full transcripts, unrestricted command output, or recalled bundle bodies.
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 · 11 lines · 181 tokens per session scan A 5383a1a9a5b9
agent-recall-trail AGENTS.md is an instructions file published in the GitHub repository fantasyce/agent-recall-trail (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 181 tokens to every session, about $0.0009 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
kb AGENTS.md
AGENTS.md instructions for hraness/kb, a project described as: A knowledge base for coding agents, built from Markdown, backlinks, semantic search, and Git context.
engraphis AGENTS.md
AGENTS.md instructions for Coding-Dev-Tools/engraphis, covering agents.md — engraphis, internal subagent delegation, 0. read this first — two architectures live in one package, 1. commands and ── unified dashboard + memory inspector ──.
brigade AGENTS.md
Instructions for escoffier-labs/brigade, covering agents.md, definition of done, rules, orientation and memory handoff.
Binder AGENTS.md
Instructions for mpazik/Binder, covering binder, tech stack, monorepo structure, testing and development.
Agent-Memory-Bridge AGENTS.md
Instructions for zzhang82/Agent-Memory-Bridge, covering agent memory bridge contributor instructions, setup and checks, architecture boundaries, mutation and migration invariants and benchmark expectations.
brain-os AGENTS.md
Instructions for brainOS-HQ/brain-os, covering agents.md, context, the hard rule, tool routing (in order) and mutation safety.