Borrowing it
Nothing to install: this file belongs to shintaro-sprech/agent-orchestrator-template. 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/shintaro-sprech/agent-orchestrator-template/main/CLAUDE.mdgit clone --depth 1 https://github.com/shintaro-sprech/agent-orchestrator-templateWrote 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/shintaro-sprech/agent-orchestrator-template/claude-md)<a href="https://agentmods.dev/instructions/shintaro-sprech/agent-orchestrator-template/claude-md"><img src="https://agentmods.dev/badge/instructions/shintaro-sprech/agent-orchestrator-template/claude-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/shintaro-sprech/agent-orchestrator-template/claude-md"><img src="https://agentmods.dev/badge/instructions/shintaro-sprech/agent-orchestrator-template/claude-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.01183 | $0.01183 |
| Opus 5 | $0.00592 | $0.00592 |
| Sonnet 5 | $0.00237 | $0.00237 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
agent-orchestrator-template CLAUDE.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 10d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - Autonomous Orchestration Ecosystem
Add this section to your project's CLAUDE.md file.
Agent Orchestration
Must: All implementation tasks must pass through the orchestrator workflow before execution.
Decision Gate Exception
An explicitly invoked analysis-only Skill may run before /task when it does not modify code, files, external systems, or production state.
Use /evaluation-first-decision to create a Decision Card containing the verdict, evidence, guardrails, stop conditions, and rollback plan.
GOorPILOTdoes not itself authorize execution.- For
HIGHorCRITICALrisk, record the responsible human decision owner. - When execution is approved, include the Decision Card in the
/taskinput. - The orchestrator must preserve the approved scope, guardrails, stop conditions, and rollback requirements.
HOLDorSTOPblocks execution until the stated verdict-changing conditions are satisfied.
Core Principle
Do NOT use pre-defined abstract agents. Instead:
- Create specialized agents from actual task requirements
- Integrate existing agents when synergy improves outcomes
- Let the agent pool evolve through continuous improvement
Workflow
Consequential decision (when applicable)
↓
/evaluation-first-decision
↓
Decision Card + human approval where required
↓
Task Received through /task
↓
Scan pool/ for existing agents
↓
Calculate coverage rate against task requirements
↓
┌─────────────────────────────────────────────────────┐
│ Coverage 90%+ → Use existing agent │
│ Coverage 60-90% → Create integrated agent │
│ Coverage <60% → Create new specialized agent │
└─────────────────────────────────────────────────────┘
↓
Execute task within approved guardrails
↓
Update manifests/ with metrics
↓
Promote to elite/ if qualified
Directory Structure
.claude/
├── skills/
│ └── evaluation-first-decision/
│ ├── SKILL.md
│ ├── references/
│ └── assets/
├── agents/
│ ├── orchestrator.md # Orchestrator definition (read first)
│ ├── _template.md # Template for new agents
│ ├── manifests/ # Skill sheets (metadata + metrics)
│ │ └── {agent-name}.yaml
│ └── pool/ # Agent pool
│ ├── specialized/ # Task-specific agents (newly created)
│ ├── integrated/ # Merged agents (1st/2nd Gen Integration)
│ └── elite/ # Hyper-Elite agents (proven performers)
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.
- 10d ago First seen · 154 lines · 1,183 tokens per session scan A e5ffe3154163
agent-orchestrator-template CLAUDE.md is an instructions file published in the GitHub repository shintaro-sprech/agent-orchestrator-template (124 stars, last pushed 10d ago), licensed MIT. It adds 1,183 tokens to every session, about $0.0059 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).
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.
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.