SCOUT: Instructions file for Codex

AGENTS.md

SCOUT AGENTS.md is an instructions file for Codex, OpenCode from R00T-Kim/SCOUT. It costs 4,919 tokens per session, scanned A, original, Apache-2.0.

A project instruction file for an autonomous coding-agent setup called oh-my-codex. It defines how agents coordinate, follow project guidance, handle tasks, and report their work.

In plain words
What is it for?
Use it to guide agent delegation, execution steps, safety checks, cancellation, state management, and the required format for project reports.
Why use it?
It gives multiple coding agents shared rules so their decisions and changes remain consistent across a project.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions subagents; reads ~/.codex paths; mentions AGENTS.md.

This is R00T-Kim/SCOUT's own configuration. It tells Codex and OpenCode how to work on SCOUT itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything SCOUT configures →

Reuse

Borrowing it

Nothing to install: this file belongs to R00T-Kim/SCOUT. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/R00T-Kim/SCOUT/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/R00T-Kim/SCOUT

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for SCOUT AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/r00t-kim/scout/agents-md/github.svg)](https://agentmods.dev/instructions/r00t-kim/scout/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/r00t-kim/scout/agents-md"><img src="https://agentmods.dev/badge/instructions/r00t-kim/scout/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for SCOUT AGENTS.md

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 4,919 This file is loaded in full into every session.
When invoked 4,919 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.04919 $0.04919
Opus 5.5 $0.01968 $0.01968
Sonnet 5.5 $0.00984 $0.00984
Haiku 4.5 $0.00492 $0.00492

Measured 1mo ago against content hash 8e0c9f693123, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

AGENTS.md · 379 lines

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>

Read the full file on GitHub · 379 lines

Changes

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.

  1. 1mo ago First seen · 379 lines · 4,919 tokens per session scan A 8e0c9f693123

Subscribe to this mod's changes

SCOUT AGENTS.md is an instructions file published in the GitHub repository R00T-Kim/SCOUT (13 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 4,919 tokens to every session, about $0.0197 per session on Opus 5.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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens