Borrowing it
Nothing to install: this file belongs to DeL-TaiseiOzaki/claude-code-orchestra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DeL-TaiseiOzaki/claude-code-orchestra/main/AGENTS.mdgit clone --depth 1 https://github.com/DeL-TaiseiOzaki/claude-code-orchestraWrote 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/del-taiseiozaki/claude-code-orchestra/agents-md)<a href="https://agentmods.dev/instructions/del-taiseiozaki/claude-code-orchestra/agents-md"><img src="https://agentmods.dev/badge/instructions/del-taiseiozaki/claude-code-orchestra/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.
<a href="https://agentmods.dev/instructions/del-taiseiozaki/claude-code-orchestra/agents-md"><img src="https://agentmods.dev/badge/instructions/del-taiseiozaki/claude-code-orchestra/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.02800 | $0.02800 |
| Opus 5 | $0.01400 | $0.01400 |
| Sonnet 5 | $0.00560 | $0.00560 |
| Haiku 4.5 | $0.00280 | $0.00280 |
Grade A, and why
claude-code-orchestra 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 4d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md -- CLI Agent Contract
Every CLI agent loads this file automatically from the repository root. It is the contract for CLI executors such as Codex, Antigravity, Grok, and opencode: response structure, handoff rules, how to call another CLI as a subagent, and the completion-verification guardrails. Follow it as written -- nothing here depends on opening another file first.
Where to go next, only as the task needs it:
| You are | Read |
|---|---|
| The main agent (Claude Code by default) | CLAUDE.md -- mission, routing policy, skill catalog, quality gates |
| Any agent needing tier details | .claude/rules/tiers.md |
| Any agent needing shared standards | .claude/rules/ -- coding, testing, security, delegation |
| Codex | .codex/AGENTS.md -- model, sandbox, enabled skills |
| Antigravity | .agents/AGENTS.md -- headless behaviour and limits |
The active main agent is recorded in .claude/STATE.md.
.claude/docs/INDEX.md is the full registry;
.claude/docs/change_main.md changes the main agent.
Required Response Structure
Always respond in the following order.
## TL;DR
- Conclusion in 3 lines or fewer
## Analysis
- Problem decomposition, assumptions, constraints
## Plan
1. Implementation step
2. Implementation step
## Patch Strategy
- Which files to change and what to change in each
## Validation
- Tests/verification commands to run
## Risks
- Impact of failure and mitigation strategies
Handoff Rules
- Return procedures that are directly executable as-is
- Compress key points needed for decision-making, not lengthy raw data
- Separate unverified items as TODOs
- State assumptions before implementing ambiguous requirements
- Prefer incremental, minimal diffs for large changes
- Include a migration plan whenever compatibility may break
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.
- 4d ago Changed · +83 lines · +1,228 tokens per session c4ec9068135d
- 9d ago First seen · 140 lines · 1,572 tokens per session scan A eacef046a85a
claude-code-orchestra AGENTS.md is an instructions file published in the GitHub repository DeL-TaiseiOzaki/claude-code-orchestra (194 stars, last pushed 5d ago), licensed MIT. It adds 2,800 tokens to every session, about $0.0140 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-30.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.