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/chacosoldier/compabob/_orchestrator-referencegit clone --depth 1 https://github.com/chacosoldier/compabobWhat 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.00000 | $0.00532 |
| Opus 5 | $0.00000 | $0.00266 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
_orchestrator-reference 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Reference
How the main session coordinates the agent fleet. Primary routing rules live in CONSTITUTION.md; this file holds the detail.
The canonical agent list and what each one is for lives in
CONSTITUTION.md(Agent Architecture & Routing). It is not repeated here, so there is one source of truth to keep current. This file covers how the main session coordinates the fleet once a request has been routed.
Routing
Match the request against each agent's description, not its name. The rules of thumb in CONSTITUTION.md cover the common cases. For ambiguous requests, ask one clarifying question rather than guessing.
When two agents seem equally plausible, prefer the narrower-scoped one. It will redirect if wrong; the broader one will absorb the task without flagging the boundary.
Negative routing (disambiguation)
| Phrase | Looks like | Routes to | Why |
|---|---|---|---|
| "challenge this plan" | a coaching ask | strategy-advisor |
An artifact is being brought for critique |
| "what's wrong with this code" | strategy-advisor |
principal-engineer |
Engineering critique, not strategic |
| "what's wrong with this plan" | principal-engineer |
strategy-advisor |
Strategic critique, not engineering |
| "what does this concept really mean" | strategy-advisor |
first-principles |
Abstract reasoning, not a decision |
| "save this to the vault" | the originating agent | second-brain |
Advice-only agents request persistence |
Pipeline patterns
Parallel fan-out, main-session fan-in (most common): spawn two independent agents at once, wait for both, synthesize, present.
Sequential chain: spawn agent A, pass its output to agent B, present.
The rule: agents produce data, the main session produces insight.
Handoff rules
- Always pass the date range used in any query so downstream agents match it.
- When passing data to an output step, provide structured tables, not prose.
- Include the query or source used so a downstream agent can verify.
- Advice-only agents (
strategy-advisor,principal-engineer,first-principles) never write files. When their output should persist, the main session hands it tosecond-brain.
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 · 41 lines · 0 tokens per session scan A cd3de11f0e1f
_orchestrator-reference is an agent published in the GitHub repository chacosoldier/compabob (32 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 532 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.
Other agents, from other repositories
observer
Background agent that analyzes session observations to detect patterns and create instincts. Uses Haiku for cost-efficiency.
mcp-server-architect
Designs and implements MCP servers with transport layers, tool/resource/prompt definitions, completion support, session management, and protocol compliance. Specializes in FastMCP 2.x async servers with real API integrations and plain text formatting for optimal LLM consumption.
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.
implementer
Mechanical execution agent for bounded, well-defined tasks. Scope and approach must be explicit in the task prompt. Use after a planner has produced a plan. For complex logic or design decisions, use Sonnet instead.
claude-code-guide
Expert on the Claude Code Ultimate Guide. Use when answering questions about Claude Code features, workflows, configuration, hooks, agents, MCP servers, costs, and best practices. Searches the guide before answering. Cites file + line sources.
tools
Give your Agents capabilities with built-in tools, MCP servers, and custom scripts.