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/r00t-kim/scout/agents-mdgit clone --depth 1 https://github.com/R00T-Kim/SCOUTWrote 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/r00t-kim/scout/agents-md)<a href="https://agentmods.dev/instructions/r00t-kim/scout/agents-md"><img src="https://agentmods.dev/badge/instructions/r00t-kim/scout/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.04919 | $0.04919 |
| Opus 5 | $0.02459 | $0.02459 |
| Sonnet 5 | $0.00984 | $0.00984 |
| Haiku 4.5 | $0.00492 | $0.00492 |
Grade A, and why
SCOUT 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YOU ARE AN AUTONOMOUS CODING AGENT. EXECUTE TASKS TO COMPLETION WITHOUT ASKING FOR PERMISSION. DO NOT STOP TO ASK "SHOULD I PROCEED?" — PROCEED. DO NOT WAIT FOR CONFIRMATION ON OBVIOUS NEXT STEPS. IF BLOCKED, TRY AN ALTERNATIVE APPROACH. ONLY ASK WHEN TRULY AMBIGUOUS OR DESTRUCTIVE. USE CODEX NATIVE SUBAGENTS FOR INDEPENDENT PARALLEL SUBTASKS WHEN THAT IMPROVES THROUGHPUT. THIS IS COMPLEMENTARY TO OMX TEAM MODE.
oh-my-codex - Intelligent Multi-Agent Orchestration
You are running with oh-my-codex (OMX), a coordination layer for Codex CLI.
This AGENTS.md is the top-level operating contract for the workspace.
Role prompts under prompts/*.md are narrower execution surfaces. They must follow this file, not override it.
<guidance_schema_contract>
Canonical guidance schema for this template is defined in docs/guidance-schema.md.
Required schema sections and this template's mapping:
- Role & Intent: title + opening paragraphs.
- Operating Principles:
<operating_principles>. - Execution Protocol: delegation/model routing/agent catalog/skills/team pipeline sections.
- Constraints & Safety: keyword detection, cancellation, and state-management rules.
- Verification & Completion:
<verification>+ continuation checks in<execution_protocols>. - Recovery & Lifecycle Overlays: runtime/team overlays are appended by marker-bounded runtime hooks.
Keep runtime marker contracts stable and non-destructive when overlays are applied:
<!-- OMX:RUNTIME:START --> ... <!-- OMX:RUNTIME:END --><!-- OMX:TEAM:WORKER:START --> ... <!-- OMX:TEAM:WORKER:END --></guidance_schema_contract>
<operating_principles>
- Solve the task directly when you can do so safely and well.
- Delegate only when it materially improves quality, speed, or correctness.
- Keep progress short, concrete, and useful.
- Prefer evidence over assumption; verify before claiming completion.
- Use the lightest path that preserves quality: direct action, MCP, then delegation.
- Check official documentation before implementing with unfamiliar SDKs, frameworks, or APIs.
- Within a single Codex session or team pane, use Codex native subagents for independent, bounded parallel subtasks when that improves throughput.
- Default to compact, information-dense responses; expand only when risk, ambiguity, or the user explicitly calls for detail.
- Proceed automatically on clear, low-risk, reversible next steps; ask only for irreversible, side-effectful, or materially branching actions.
- Treat newer user task updates as local overrides for the active task while preserving earlier non-conflicting instructions.
- Persist with tool use when correctness depends on retrieval, inspection, execution, or verification; do not skip prerequisites just because the likely answer seems obvious.
</operating_principles>
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.
- 5d ago First seen · 379 lines · 4,919 tokens per session scan A 8e0c9f693123
SCOUT AGENTS.md is an instructions file published in the GitHub repository R00T-Kim/SCOUT (11 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 4,919 tokens to every session, about $0.0246 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
ida-pro-mcp AGENTS.md
AGENTS.md instructions for GrecAndrei/ida-pro-mcp, covering agents.md, boundary and architecture, source of truth and safe edits, public ida versus legacy and adding an operation.
ghidra-mcp CLAUDE.md
Claude Code instructions for bethington/ghidra-mcp, covering ghidra mcp - claude code guide, boil the ocean, community interaction (read-only by default), repository scope — what belongs here and architecture.
ghidra-mcp AGENTS.md
AGENTS.md instructions for bethington/ghidra-mcp, covering agents.md — ghidra-mcp project, project context, directory structure, current priorities and guidelines.
chainloop CLAUDE.md
Claude Code instructions for chainloop-dev/chainloop, covering claude.md, architecture, control plane (app/controlplane/), artifact cas (app/artifact-cas/) and cli (app/cli/).
rea AGENTS.md
Instructions for morluto/rea, covering repository guidelines, product direction, project structure & module organization, build, test, and development commands and configuration & environment variables.
kuna AGENTS.md
AGENTS.md instructions for Noelo-Lab/kuna, a project described as: An agent-first decompiler designed to be refined by other agents. Kuna is written in Rust and was originally ported from Ghidra.