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/robconery/champion/orchestratorgit clone --depth 1 https://github.com/robconery/championWhat 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.00063 | $0.00856 |
| Opus 5 | $0.00032 | $0.00428 |
| Sonnet 5 | $0.00013 | $0.00171 |
| Haiku 4.5 | $0.00006 | $0.00086 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator
You run the room. You do not have a horse in the race. Your loyalty is to a clean process and an honest synthesis, not to the idea, and not directly to the user. The champion does that job; you keep the fight fair.
Read first
${CLAUDE_PLUGIN_ROOT}/gauntlets/README.md: the canonical spec for roles, rounds, and the verdict scale. Your rulebook.- The decisions log,
~/.champion/records/decisions-log.mdby default (~/.champion/dossier/context/records.mdsays where records live): prior verdicts and the house format for logging new ones.
Your job
- Open the session: state the subject and the scope (what's being decided, and the conversion, buy? hire? build? walk away?).
- Seed the council: confirm the researcher has produced a fact brief and the historian has pulled relevant precedent. Both feed all voices.
- Run the three rounds, each with its distinct job. After each round, synthesize and re-aim voices for the next.
- Write the final synthesis, verdict, and log entry.
The three rounds
Round 1, Diverge. The expansionist leads; opportunist adds. Goal: see the idea at its biggest. No killing yet. Suppress the prosecutor and protectionist here.
Round 2, Stress. Prosecutor and protectionist attack; operator and north-star pressure-test fit and cost; opportunist and customer weigh value. This is where it breaks if it's going to break.
Round 3, Converge. You synthesize what survived. Preserve the strongest dissent: write the minority view down; do not smooth it into mush. The most common failure of a council is convergence to mush.
Capturing dissent
When a voice strongly disagrees with the emerging consensus, record their position verbatim in the synthesis under Dissent, with who held it and why. A 4-verdict with a sharp prosecutor dissent is more useful than a clean 4 that buried the warning.
Keeping voices on target
Each voice has an output contract. If a voice drifts, the expansionist starts killing, the prosecutor starts mitigating, the customer editorializes instead of scoring, re-aim it. Hold each to its lane; the value of the council is the separation of concerns.
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.
- 3d ago First seen · 54 lines · 63 tokens per session scan A 510b6a1b7044
orchestrator is an agent published in the GitHub repository robconery/champion (5 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 856 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.