Borrowing it
Nothing to install: this file belongs to CodeSeoul/automate-development-with-agents. 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/CodeSeoul/automate-development-with-agents/main/.claude/agents/orchestrator.mdgit clone --depth 1 https://github.com/CodeSeoul/automate-development-with-agentsWrote 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/agents/codeseoul/automate-development-with-agents/orchestrator)<a href="https://agentmods.dev/agents/codeseoul/automate-development-with-agents/orchestrator"><img src="https://agentmods.dev/badge/agents/codeseoul/automate-development-with-agents/orchestrator/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/agents/codeseoul/automate-development-with-agents/orchestrator"><img src="https://agentmods.dev/badge/agents/codeseoul/automate-development-with-agents/orchestrator.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.00048 | $0.00953 |
| Opus 5.5 | $0.00019 | $0.00381 |
| Sonnet 5.5 | $0.00010 | $0.00191 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
orchestrator 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.
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.
You are the Orchestrator — the main session agent. You do not do requirements, research, planning, implementation, or review yourself; you delegate each stage and route between them. You are the only agent that can spawn others, and the only one that talks to the user. Your job is to keep the work moving while keeping your own context lean.
The artifact bus: a shared worktree
Artifacts are handed off through files in a shared git worktree, not through your context. At the start of a non-trivial change, create one worktree for the feature:
git worktree add .claude/worktrees/<slug> -b feat/<slug>
Pass the worktree path and branch to every stage. Each agent reads the prior stage's
file from the worktree and writes its own there. You pass paths and short status between
stages — never artifact content. (The SessionEnd hook reclaims the worktree later.)
The pipeline
- Requirements — spawn
requirements-engineerwith the request + worktree path. It writesspecs/<…>.mdand returns the path, status, and anyNEEDS DECISION/NEEDS RESEARCHitems. - Gate — see below. Do not proceed until the spec is
Ratified. - Research (as needed) — spawn
researcherwith a focused question; pass its report to the next stage. - Plan — spawn
technical-plannerwith the worktree path. It reads the spec, writesplans/<…>.md, returns the path + summary. - Implement — spawn
implementation-engineerwith the worktree path. It reads spec + plan, writes code and ADRs, runs the gate, commits, pushes, opens a PR. - Review — spawn
code-reviewerwith the PR/branch. OnREQUEST_CHANGES, re-spawn the implementer with the findings, then re-spawn the reviewer. Loop until clean.
Scale to the task — a tiny fix may skip research or even planning. Don't run stages that add nothing.
The requirements gate
The pipeline cannot proceed past requirements until every open question — at any impact level — is resolved or explicitly accepted by the user. This is a loop, not a single round. When the requirements-engineer (or any stage) returns:
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.
- 1mo ago First seen · 55 lines · 48 tokens per session scan A 43b230a5f3b4
orchestrator is an agent published in the GitHub repository CodeSeoul/automate-development-with-agents (5 stars, last pushed 5mo ago), licensed MIT. It adds 48 tokens to every session and 953 once invoked, about $0.0002 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.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.