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/menugit clone --depth 1 https://github.com/mbruhler/claude-orchestrationWrote 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/commands/mbruhler/claude-orchestration/menu)<a href="https://agentmods.dev/commands/mbruhler/claude-orchestration/menu"><img src="https://agentmods.dev/badge/commands/mbruhler/claude-orchestration/menu.svg" alt="Measured on agentmods" 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 | $0.00006 | $0.00921 |
| Opus 5 | $0.00003 | $0.00461 |
| Sonnet 5 | $0.00001 | $0.00184 |
| Haiku 4.5 | $0.00001 | $0.00092 |
Grade A, and why
menu 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestration Menu
You are in Menu Mode of the Workflow Orchestration System. Present an interactive menu to guide the user through available orchestration features.
Arguments: {{ARGS}}
Display Menu
Use AskUserQuestion to present the main menu:
AskUserQuestion({
questions: [{
question: "What would you like to do?",
header: "Menu",
multiSelect: false,
options: [
{label: "Import agents", description: "Import custom agents from Claude Code"},
{label: "Create from description", description: "Natural language workflow creation"},
{label: "New workflow", description: "Create workflow from syntax"},
{label: "Load template", description: "Execute saved flow"},
{label: "Manage syntax", description: "View/edit global syntax library"},
{label: "View docs", description: "Help, examples, or topic guides"}
]
}]
})
Handler Actions
Import agents
- Execute
/orchestration:init - Imports custom agents from ~/.claude/agents/ to orchestration plugin
- Makes them available for use in workflows with orchestration: namespace
Create from description
- Execute
/orchestration:create - This launches the natural language workflow creation flow
New workflow
- Prompt for workflow syntax
- Execute
/orchestration:run <syntax>
Load template
- Show available templates from:
./workflows/(project root)~/.claude/workflows/(Claude root)~/.claude/plugins/repos/orchestration/examples/(built-in)
- Let user select template
- Execute
/orchestration:template <template-name>
Manage syntax
Present submenu for global syntax management using AskUserQuestion:
AskUserQuestion({
questions: [{
question: "Manage global syntax library:",
header: "Syntax",
multiSelect: false,
options: [
{label: "List all syntax", description: "Show all global syntax elements"},
{label: "View by type", description: "Browse operators, actions, etc."},
{label: "Search syntax", description: "Find specific syntax elements"},
{label: "Back to menu", description: "Return to main menu"}
]
}]
})
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 · 135 lines · 6 tokens per session scan A df53113be4ac
menu is a command published in the GitHub repository mbruhler/claude-orchestration (218 stars, last pushed 3mo ago), licensed MIT. It adds 6 tokens to every session and 921 once invoked, about $0.0000 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.