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 commands/mbruhler/claude-orchestration/initgit clone --depth 1 https://github.com/mbruhler/claude-orchestrationWhat 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.00011 | $0.00902 |
| Opus 5 | $0.00005 | $0.00451 |
| Sonnet 5 | $0.00002 | $0.00180 |
| Haiku 4.5 | $0.00001 | $0.00090 |
Grade A, and why
init 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Orchestration Plugin
Import custom agents from your Claude Code environment to make them available in orchestration workflows.
Usage
/orchestration:init
This command will:
- Scan
~/.claude/agents/for custom agent definitions - Let you select which agents to register
- Make agents available for use in all workflows
Action
IMPORTANT: Execute ALL steps in order. Use AskUserQuestion for user choices.
Step 1: Scan for Custom Agents
- Use Glob tool to find all
.mdfiles in~/.claude/agents/ - Filter out built-in agents:
explore,plan,general-purpose - For each custom agent file:
- Read the file using Read tool
- Extract description from frontmatter or first heading
- Store agent name and description
- If no custom agents found, inform user and exit
Step 2: Present Agents to User
IMPORTANT: MUST use AskUserQuestion tool for interactive selection!
If custom agents were found:
- Create options array from discovered agents
- Each option should have:
label: agent name (e.g., "expert-code-implementer")description: agent description or "No description available"
- Use AskUserQuestion tool:
question: "Select agents to register in orchestration context. These agents will become available for use in workflows."header: "Import Agents"multiSelect: true (allow multiple selections)options: the options array (max 4, if more agents exist, add "Import all" option)
- Parse the response to get list of selected agent names
Step 3: Register Selected Agents
For each selected agent:
- Read the agent file from
~/.claude/agents/{agent-name}.md - Extract metadata (name, description)
- Create reference mapping (do NOT copy the file!)
- Store mapping with:
- Agent name
- Description
- Path to original file:
~/.claude/agents/{agent-name}.md - Type: "external"
Step 4: Update Agent Registry
IMPORTANT: Use ${CLAUDE_PLUGIN_ROOT} for all plugin workspace paths!
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 · 124 lines · 11 tokens per session scan A 51f5c1e6207a
init is a command published in the GitHub repository mbruhler/claude-orchestration (218 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 902 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 commands, from other repositories
claude-flow-swarm
Coordinate multi-agent swarms for complex tasks.
bootstrap
PACT session-start ritual — identify the session team (platform-provisioned), secretary spawn, paused-state surface, bootstrap marker.
ox-session-review
Command "ox-session-review" from sageox/ox, covering failure-mode watch-list (read first), from the ledger root. should print 0, phase 1 — scan & score (read-only), quality buckets (first match wins) and removal candidates.
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
handoff
Package current state for the next agent.
xdo
Direct development by the Main Agent.