ORCHESTRATION

A guide for coordinating seven coding agents, each with a defined role such as planning, implementation, verification, interface design, or pull-request review.

In plain words
What is it for?
It is for choosing between solo development and delegated team work, assigning implementation and verification roles, and coordinating pull requests toward completion.
Why use it?
It helps decide which agent should handle a task and explains how agents divide work, especially when a change is too large for one person.

Agent

Install

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.

agentmods
npx agentmods add agents/boraoztunc/agent-system/orchestration
Clone the repo
git clone --depth 1 https://github.com/boraoztunc/agent-system
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,151 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.02151
Opus 5 $0.00000 $0.01076
Sonnet 5 $0.00000 $0.00430
Haiku 4.5 $0.00000 $0.00215

Measured 3d ago against content hash 364179011d95, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ORCHESTRATION 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 3d 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/ORCHESTRATION.md · 229 lines

How it starts

The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent System — Orchestration Spec

How the 7 agents work together across any project.


Agent Roster

Agent Role Edits Code? Delegates? Works Alone?
Coordinator Plans, delegates, verifies. Orchestrates multi-agent workflows. No Yes No
Developer Plans AND implements. Solo end-to-end agent. Yes No Yes
Implementor Executes a single task from a task note. Minimal scope. Yes No No
Verifier Evidence-based verification against acceptance criteria. No No No
UI Designer Builds accessible, design-system-consistent interfaces. Yes No No
PR Reviewer Reviews PR diffs for bugs, security, correctness. No Yes (to Implementor) No
PR Shepherd Shepherds a PR to merge-ready state (CI green, comments resolved). No Yes (to Implementor) No

When to Use Which Agent

Decision tree: Start here

Is this a PR that needs review or shepherding?
├── YES: reviewing code? → PR Reviewer
├── YES: getting to green/merge-ready? → PR Shepherd
└── NO: building/changing something
    ├── Small/focused task (1-3 files, one area)?
    │   └── Developer
    └── Large feature (4+ files, multiple areas, parallelizable)?
        └── Coordinator → delegates to Implementors / UI Designers

Quick reference

Scenario Agent Why
Fix a single bug Developer Focused, no overhead
Add a small feature Developer Plans + implements, fast iteration
Build a multi-part feature Coordinator Parallel implementors, independent verification
Implement a UI component UI Designer (under Coordinator) or Developer UI Designer if accessibility/design-system compliance matters
Review a PR before merge PR Reviewer High-signal code review
PR has failing CI or open comments PR Shepherd Loops until green
Verify implementation against spec Verifier Evidence-driven, no bias
Quick iteration / follow-up fixes Developer Low ceremony, fast

Read the full file on GitHub · 229 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. 3d ago First seen · 229 lines · 0 tokens per session scan A 364179011d95

Subscribe to this mod's changes

ORCHESTRATION is an agent published in the GitHub repository boraoztunc/agent-system (11 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,151 tokens. 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.