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/jeroromano/claude-code-orchestration-template/claude-mdgit clone --depth 1 https://github.com/jeroromano/claude-code-orchestration-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/jeroromano/claude-code-orchestration-template/claude-md)<a href="https://agentmods.dev/instructions/jeroromano/claude-code-orchestration-template/claude-md"><img src="https://agentmods.dev/badge/instructions/jeroromano/claude-code-orchestration-template/claude-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.01503 | $0.01503 |
| Opus 5 | $0.00751 | $0.00751 |
| Sonnet 5 | $0.00301 | $0.00301 |
| Haiku 4.5 | $0.00150 | $0.00150 |
Grade A, and why
claude-code-orchestration-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 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
- Orchestration Policy
Model routing
- Default main model: Opus or Sonnet. Never use the most expensive available model for mechanical work.
- Escalating the main model (e.g. to Fable) is a human decision (
/model), reserved for architecture, hard multi-module bugs, and design sessions. Suggest escalation when warranted; never assume it. - Design sessions must end with a written spec in
docs/specs/before any implementation starts. - An APPROVED design or spec authored by the escalated top tier is AUTHORITATIVE for the cheaper model implementing it: implement to the letter, each point a checklist item - no silent simplification, no substituting a specified check with "equivalent" reasoning of your own. Flag any deviation to the human BEFORE deviating. Only overrides: an independent review catches a concrete error (repro or file:line), or an explicit human decision. Audit and review findings are NOT specs: they enter the finding-validation flow (skill §6) and are never auto-applied.
- Architecture, planning and specs are authored on the main Claude thread (Fable when escalated); never delegate them to Codex.
- Never use Codex Ultra or any external multi-agent orchestration mode: this policy is the orchestration layer - Ultra would duplicate it.
Delegation
Mechanics live in the delegation-protocol skill - use it for any delegation or review. Summary:
- Mechanical, fully-specified work -> fast-worker agent.
- Scoped implementation with an approved spec -> Codex rescue if the Codex plugin is installed (Sol where the account has it - model-unavailable fallback in the skill §5; effort medium; high only for hard bugs or multi-module work), background; otherwise fast-worker. Exact command in the skill.
- Sol's primary role is independent audit of Claude-authored diffs; writing is secondary and always spec-bound.
- One hard scoped question -> deep-reasoner agent.
- Beyond deep-reasoner -> premium-reasoner agent, ONLY with explicit human authorization per invocation: the orchestrator adds the token PREMIUM-APPROVED to the delegation prompt if and only if the human authorized premium spend for that question in this session. Never auto-delegate to it.
- Every writing delegation carries the full task spec (goal, allowed files, non-goals, acceptance, validation, expected diff shape).
- Every delegated report opens with a provenance line (agent, model, effort - tiers and Codex caveats in the skill §4); the orchestrator closes each result with harness-reported token usage. No money figures; pool attribution is the human's check via /usage.
- One writer per file. Parallel writers only on separate branches/worktrees.
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 · 55 lines · 1,503 tokens per session scan A 99ffdc82a8f9
claude-code-orchestration-template CLAUDE.md is an instructions file published in the GitHub repository jeroromano/claude-code-orchestration-template (1 stars, last pushed 26d ago), licensed MIT. It adds 1,503 tokens to every session, about $0.0075 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
vibe-coding-prompt-template backend.instructions.md
Instructions for KhazP/vibe-coding-prompt-template: Read AGENTS.md, agentdocs/techstack.md, and agentdocs/codepatterns.md.
Library-First-Engineering copilot-instructions.md
Instructions for StChiotis/Library-First-Engineering: You are an AI agent operating in a Library-First Engineering (LFE) repository. This adapter is a pointer. Canonical rules live in human-readable docs.
festival GEMINI.md
Gemini CLI instructions for Obedience-Corp/festival: Festival is a goal-oriented project management methodology for human and AI development workflows, driven by the fest and camp CLIs, installed and kept in sync by a third tool, festival. The skills imported below describe how to plan and execute festivals. Load them…
unity-ai-workflow CLAUDE.md
Instructions for devdavv/unity-ai-workflow, covering unity ai workflow, workspace layout, project config, dev modes and non-negotiable rules.
daily-watchlist CLAUDE.md
Instructions for Benboerba620/daily-watchlist: This file is the source protocol for the Daily Watchlist workflow. Hypothesis Tracker is bundled in this repository as the thesis/evidence layer.
ai-auto-work CLAUDE.md
Claude Code instructions for chaohong-ai/ai-auto-work, covering gamemaker - ai native 游戏创作平台, 项目简介, ai 工作目录约定 and 按需加载（不默认装载）.