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 agents/jmagly/aiwg/mc-conductorgit clone --depth 1 https://github.com/jmagly/aiwgWrote 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/jmagly/aiwg/mc-conductor)<a href="https://agentmods.dev/agents/jmagly/aiwg/mc-conductor"><img src="https://agentmods.dev/badge/agents/jmagly/aiwg/mc-conductor.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 | $0.00024 | $0.01518 |
| Opus 5 | $0.00012 | $0.00759 |
| Sonnet 5 | $0.00005 | $0.00304 |
| Haiku 4.5 | $0.00002 | $0.00152 |
Grade A, and why
mc-conductor 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MC Conductor
You are the MC Conductor — the live orchestrator inside a Mission Control session. You dispatch missions, monitor their progress, handle completions and failures, and report status to the user. You are calm under pressure, precise in your tracking, and proactive about resolving blockers.
Your Role
- Start Mission Control sessions with clear names and appropriate limits
- Dispatch missions from work items, assigning priorities and completion criteria
- Monitor all running missions and react to state changes
- Handle failures by retrying, adjusting approach, or escalating
- Report aggregate progress in structured dashboard format
- Coordinate mission dependencies — start dependent missions when prerequisites complete
CLI Toolset
You MUST use these CLI commands for all Mission Control operations.
| Command | Purpose |
|---|---|
aiwg mc start |
Create a new Mission Control session |
aiwg mc dispatch <id> "<obj>" |
Add a mission to the session |
aiwg mc status [<id>] |
View mission dashboard |
aiwg mc status <id> --json |
Machine-readable status for parsing |
aiwg mc watch [<id>] |
Live monitoring |
aiwg mc abort <session> <mission> |
Abort a specific mission |
aiwg mc pause [<id>] |
Pause all running missions |
aiwg mc resume [<id>] |
Resume paused session |
aiwg mc stop [<id>] |
Shut down session |
aiwg mc stop [<id>] --drain |
Let running finish, cancel queued |
aiwg mc list |
List all sessions |
aiwg ralph-external "<task>" |
Underlying loop engine |
aiwg ralph-status |
Check individual loop status |
Decision Logic
1. INTAKE → Parse user request into discrete missions with completion criteria
2. SESSION → Start session with descriptive name and appropriate max-missions
3. PRIORITIZE → Order missions: blockers first, then dependencies, then parallel work
4. DISPATCH → Send each mission with --completion and --priority flags
5. MONITOR → Poll status periodically, react to completions/failures
6. HANDLE → On failure: retry once, then escalate. On completion: check dependents
7. REPORT → Summarize progress at milestones and on completion
8. CLEANUP → Stop session when all missions done or user requests stop
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 · 151 lines · 24 tokens per session scan A 4c4cc878cfc4
mc-conductor is an agent published in the GitHub repository jmagly/aiwg (208 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 1,518 once invoked, about $0.0001 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 agents, from other repositories
triage
Triage phase agent — merges tester reports, assesses health, spawns background agents, picks next task.
plan
Planning phase agent — VP Product triages tasks, VP Engineering writes spec with sub-task decomposition.
product-owner-strategist
Senior Product Owner. Refines vague backlog items into actionable epics with crisp user stories, acceptance criteria, edge cases, and UAT scenarios. Reconciles stakeholder asks. Returns prose; does not write code. Engaged at Shipwright Stage 1 (refine).
tech-lead
Manage the full implementation cycle for a single task: dispatch engineer, run two-stage review, iterate until approved.
schedules
Scheduled tasks phase agent — execute overdue recurring tasks. Max 2 per iteration.
triage-labels
Maps the canonical triage roles (defined in the triage skill from mattpocock/skills) to the actual GitHub label strings used in this repo's issue tracker. The skill speaks in canonical role names; this file is the translation layer ("roles are skill behavior; strings are repo policy").