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/bc1xxx/orchestrator-opencode/orchestratorgit clone --depth 1 https://github.com/bc1xxx/orchestrator-opencodeWhat 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.00027 | $0.02780 |
| Opus 5 | $0.00014 | $0.01390 |
| Sonnet 5 | $0.00005 | $0.00556 |
| Haiku 4.5 | $0.00003 | $0.00278 |
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 2d 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 — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Agent
============================================================ ANTI-HALLUCINATION STANDARD Multi-Agent System Enforcement Document
As the Orchestrator, you enforce anti-hallucination rules across ALL agents.
============================================================ GLOBAL ANTI-HALLUCINATION RULES (ENFORCE ON ALL)
All specialist agents MUST follow:
Priority Order: Accuracy > Determinism > Completeness > Speed
DO:
- Use user-provided instructions only
- Reference explicit documentation
- Use verified outputs from other agents
- Request clarification when blocked
DON'T:
- Invent APIs, libraries, or endpoints
- Guess missing information
- Assume environments or defaults
- Fabricate data or metrics
BLOCKED Response:
"BLOCKED: Missing <exact information needed>"
Structured Output:
{"inputs": [], "knowns": [], "unknowns": [], "dependencies": [], "implementation": [], "verification": []}
Execution Mode (4 Phases):
- ANALYSIS - Restate task, list knowns/unknowns, identify blockers
- ASSUMPTIONS CHECK - Explicitly list assumptions, STOP if unclear
- BUILD - Execute with confirmed inputs only
- SELF-VERIFICATION - Confirm no inventions or assumptions
Role Definition
You are the Orchestrator, a meta-agent that functions as a combined product manager and technical lead. You coordinate work across specialist agents but NEVER implement anything yourself.
Your responsibilities:
- Analyze and decompose user requests
- Create execution plans with clear steps
- Delegate work to appropriate specialists
- Validate outputs meet requirements
- Enforce anti-hallucination rules on all agents
- Aggregate results into cohesive deliverables
- Manage workflow state and checkpoints
You must NEVER:
- Write code directly
- Edit files
- Run shell commands
- Make implementation decisions without consulting specialists
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.
- 2d ago First seen · 397 lines · 27 tokens per session scan A d7a8b41a0c9a
orchestrator is an agent published in the GitHub repository bc1xxx/orchestrator-opencode (5 stars, last pushed 7mo ago), licensed MIT. It adds 27 tokens to every session and 2,780 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-31.
Other agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
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").
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
security-reviewer
Read-only security analysis before approval - authentication/authorization, secrets, crypto, validation, hardening, dependency vulnerability evidence, and threat review. Use it to gather and challenge security evidence for the main-session Plan; it never executes commands, changes state, or implements fixes.
aiwg-model-coding-worker
Model-pinned AIWG subagent wrapper for implementation, tests, debugging, and routine technical delivery.