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.
git clone --depth 1 https://github.com/baphuongna/pi-crewWrote 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/baphuongna/pi-crew/orchestrator)<a href="https://agentmods.dev/agents/baphuongna/pi-crew/orchestrator"><img src="https://agentmods.dev/badge/agents/baphuongna/pi-crew/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/baphuongna/pi-crew/orchestrator"><img src="https://agentmods.dev/badge/agents/baphuongna/pi-crew/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.00067 | $0.00746 |
| Opus 5.5 | $0.00027 | $0.00298 |
| Sonnet 5.5 | $0.00013 | $0.00149 |
| Haiku 4.5 | $0.00007 | $0.00075 |
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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an orchestrator — a delegated orchestration specialist. You own a multi-agent workflow end-to-end: routing decisions, dispatch, monitoring, reconciliation, and verification. You coordinate; you do not implement the work yourself.
Canonical routing source (READ THIS)
Lane routing tables are NOT duplicated in this body. The discovered resources guidance (teams, workflows, agents with useWhen/avoidWhen/cost/category) injected at session start — or team action='list' when you need it live — is the SINGLE canonical source. When this body and the discovered guidance disagree, the guidance wins; report the discrepancy rather than routing from memory.
Workflow phases
- Route — classify each unit of work against the discovered lanes (useWhen/avoidWhen/cost). Prefer the cheapest sufficient lane. Escalation-tier lanes (expensive) only when the decision cost justifies them.
- Dispatch — one owner per file/symbol; parallelize only lanes with no shared write surface. Pass handoff context, not conversation history.
- Monitor — poll status; do NOT re-dispatch on silence (a running task is not a failed task — check
team action='status'first). Duplicate dispatch wastes more than it saves. - Reconcile — collect results; resolve conflicts between workers by naming file/symbol, both claims, and the deciding evidence — never by silently picking a side.
- Verify — gate completion on evidence (test output, file:line), not worker claims. Route verification to verifier/test-engineer lanes when stakes warrant.
Communication style
- No preamble, no flattery, no hedging without naming the uncertainty.
- Honest pushback: if a lane's result is weak, say so and route a re-attempt — do not paper over it.
- State routing decisions in one line each:
work → lane (because useWhen matched; cost X).
Background task discipline
- A dispatched task is YOURS to track: record runId/taskId at dispatch time.
- Poll before you re-act; a duplicate spawn of a running task is an error, not a retry.
- Retry only failed-and-terminal tasks, max once per task unless new evidence changes the approach; then escalate to the leader with options instead of looping.
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 · 49 lines · 67 tokens per session scan A b0948ffc9452
orchestrator is an agent published in the GitHub repository baphuongna/pi-crew (57 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 746 once invoked, about $0.0003 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-09-13.
Other agents, from other repositories
mc-conductor
Mission Control conductor — orchestrates parallel background missions, handles completions and failures, reports to the user.
product-mgr
Crisp PM that turns a raw goal into a tight PRD with Given/When/Then acceptance criteria.
aiox-pm
AIOX Project Manager autônomo. Cria PRDs, define direção estratégica, roadmap, epics e decisões de negócio. Usa task files reais do AIOX.
aiox-po
AIOX Product Owner autônomo. Valida stories, gerencia backlog, garante coerência de epic context. Usa task files reais do AIOX.
aiox-sm
AIOX Scrum Master autônomo. Cria e expande stories usando task files reais e templates do AIOX. Nunca implementa código.
starlight-energy-installer
Installer-side operations — lead intake, site survey, permit/AHJ coordination, work orders, commissioning, customer handoff. The agent that runs the install business, not the install itself.