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/wolfe-jam/rust-faf-mcp/agents-mdgit clone --depth 1 https://github.com/Wolfe-Jam/rust-faf-mcpWrote 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/wolfe-jam/rust-faf-mcp/agents-md)<a href="https://agentmods.dev/instructions/wolfe-jam/rust-faf-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/wolfe-jam/rust-faf-mcp/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.02170 | $0.02170 |
| Opus 5 | $0.01085 | $0.01085 |
| Sonnet 5 | $0.00434 | $0.00434 |
| Haiku 4.5 | $0.00217 | $0.00217 |
Grade A, and why
rust-faf-mcp 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.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — rust-faf-mcp
This repository is the example of BEST on the FAF side of the ladder — not a slogan.
NONE → GOOD → BETTER → BEST
- BETTER is protocol honesty (mcp-better
main/mcp-better-better). Noproject.fafrequired. - BEST print slice (mcp-better
better-best/*/mcp-better-best) is the same software plusproject.faf. Falsifiable diff. That is the definition. - This crate is BEST on main: Trophy
project.fafand thisAGENTS.md. FAF defines. This file instructs. Sealed BLOCK from the DNA; working brief outside the markers. It is also a FAF MCP server, in Rust,one.faf/rust-faf-mcp— a crate people actually watch.
Do not collapse BETTER into BEST. Do not treat this markdown as the score. The score is project.faf (Mk4 100% ✪).
Read project.faf first. Do not edit the BLOCK. Refresh it with faf_agents. Everything below the BLOCK is how we work in this tree.
AGENTS.md — rust-faf-mcp
Rust MCP server for FAF (Foundational AI-context Format) — IANA-registered application/vnd.faf+yaml — Rust · v0.7.1
Authored by faf — do not edit the managed block; refresh with
faf export --agents. Hand content outside<!-- faf:start -->…<!-- faf:end -->is preserved.
Setup & build
cargo build # build
cargo fmt --check # fmt
cargo publish # publish
Run the tests
cargo test
cargo clippy -- -D warnings
Where things live
Cargo.tomlsrc/main.rssrc/server.rssrc/tools.rsREADME.mdLICENSE
Guardrails
- Always OK: read the tree · run the tests (
cargo test) · build the project ·cargo clippy -- -D warnings. - Ask first: dependency installs, deletions, migrations, schema changes, publish/release.
- Never: force-push · push straight to
main(branch and open a PR) · commit secrets.
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 · +53 lines · -30 tokens per session 225b216a7f8c
- 5d ago First seen · 132 lines · 2,200 tokens per session scan A e8822fafa1aa
rust-faf-mcp AGENTS.md is an instructions file published in the GitHub repository Wolfe-Jam/rust-faf-mcp (4 stars, last pushed 2d ago), licensed MIT. It adds 2,170 tokens to every session, about $0.0109 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
bun-sticky-faf CLAUDE.md
Instructions for Wolfe-Jam/bun-sticky-faf, covering claude.md — bun-sticky, what this is, stack, context and bun-sticky.
faf-cli AGENTS.md
AGENTS.md instructions for Wolfe-Jam/faf-cli, covering agents.md — faf-cli, setup & build, run the tests, where things live and conventions.
faf-cli copilot-instructions.md
Copilot instructions for Wolfe-Jam/faf-cli, covering github copilot instructions — faf-cli v6, tech stack and project context.
faf-cli CLAUDE.md
Claude Code instructions for Wolfe-Jam/faf-cli, covering claude.md — faf-cli, what this is, stack and context.
faf-cli GEMINI.md
Gemini CLI instructions for Wolfe-Jam/faf-cli, covering gemini.md — faf-cli v6 and stack.
claude-faf-mcp CLAUDE.md
Claude Code instructions for Wolfe-Jam/claude-faf-mcp, covering claude.md — claude-faf-mcp, what this is, stack and context.