Borrowing it
Nothing to install: this file belongs to chacosoldier/compabob. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chacosoldier/compabob/main/.claude/agents/_orchestrator-reference.mdgit clone --depth 1 https://github.com/chacosoldier/compabobWrote 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/chacosoldier/compabob/_orchestrator-reference)<a href="https://agentmods.dev/agents/chacosoldier/compabob/_orchestrator-reference"><img src="https://agentmods.dev/badge/agents/chacosoldier/compabob/_orchestrator-reference/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/chacosoldier/compabob/_orchestrator-reference"><img src="https://agentmods.dev/badge/agents/chacosoldier/compabob/_orchestrator-reference.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.00000 | $0.00568 |
| Opus 5.5 | $0.00000 | $0.00227 |
| Sonnet 5.5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
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 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 — 42 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. - Verification goes to
skeptic, never back to the agent that produced the finding. Give it the claims and the files, not your conclusion, so its check is independent.
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 Changed · +1 lines 7504b79a58e2
- 1mo ago First seen · 41 lines · 0 tokens per session scan A cd3de11f0e1f
_orchestrator-reference is an agent published in the GitHub repository chacosoldier/compabob (34 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 568 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
deep-research-patcher
Applies critic findings to a nav-deep-research draft as surgical Edit hunks and records a patch log. Tool-locked so it cannot regenerate the report. Spawned once at step 5 by the nav-deep-research skill.
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
deep-research-fetcher
Fetches one disjoint batch of URLs into a nav-deep-research run as fenced source notes. Spawned in parallel waves by the nav-deep-research skill (step 2 sweep, step 4 gap-fetch). Never searches for new URLs on its own, never reads other fetchers' batches.
stock-balance-sheet-reviewer
Specialist for US-stock balance-sheet health review — leverage (Net Debt/EBITDA), liquidity (current ratio, cash runway), goodwill concentration and impairment history, working capital trends (DSO, inventory days), off-balance-sheet items (commitments, contingencies), and pension underfunding. Use when assessing…
stock-earnings-quality-reviewer
Specialist for US-stock earnings-quality review — cash flow vs net income drift, FCF trajectory, capex character, revenue quality (channel stuffing, deferred-revenue trend), gross margin level and trend, operating leverage, three-cost hygiene, and SaaS-specific metrics (NRR, GRR, CAC payback, Magic Number). Use when…
go-security-reviewer
Go security vulnerability reviewer covering OWASP Top 10, injection (SQL/command/path traversal), auth/authz bypass, crypto misuse, secrets exposure, SSRF, and input validation. Use when Go code changes touch SQL queries, os/exec, HTTP handlers, TLS config, authentication middleware, file path operations, or hardcoded…