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/gregbenn7/roost/agents-mdgit clone --depth 1 https://github.com/Gregbenn7/roostWhat 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.00074 | $0.00074 |
| Opus 5 | $0.00037 | $0.00037 |
| Sonnet 5 | $0.00015 | $0.00015 |
| Haiku 4.5 | $0.00007 | $0.00007 |
Grade A, and why
roost 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.
This is a copy
100% identical to wacrm AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
This is NOT the Next.js you know
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices.
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 First seen · 6 lines · 74 tokens per session scan A e3447d842518
roost AGENTS.md is an instructions file published in the GitHub repository Gregbenn7/roost (2 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to wacrm AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
decapod AGENTS.md
Instructions for DecapodLabs/decapod, covering agents.md — universal agent contract, mandatory orientation, mandatory prompt safety gate, mandatory initialization and control-plane first loop.
decapod CLAUDE.md
Instructions for DecapodLabs/decapod, covering claude.md - agent entrypoint, orientation & documentation, mandatory prompt safety gate, project context and quick start.
gate22 AGENTS.md
Instructions for aipotheosis-labs/gate22, covering agents.md, project overview, repository structure, backend and code style & quality.
decapod GEMINI.md
Instructions for DecapodLabs/decapod, covering gemini.md - agent entrypoint, orientation & documentation, mandatory prompt safety gate, project context and quick start.
langgraph AGENTS.md
Instructions for langchain-ai/langgraph, covering agents instructions, corridor security analysis, libraries and dependency map.
agentgateway copilot-instructions.md
Instructions for agentgateway/agentgateway: Do not check for, speculate about, or report compilation errors during code review. Compilation diagnostics from review are frequently incorrect; rely on CI to detect and report compilation failures.