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/examplesgit 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.00007 | $0.00549 |
| Opus 5 | $0.00003 | $0.00275 |
| Sonnet 5 | $0.00001 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
examples 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ DEPRECATED: Orchestration Examples Gallery
This command is deprecated. Examples are now integrated into skills with detailed explanations.
Migration Guide
See examples in skills:
- creating-workflows/examples.md - Complete workflow examples
- creating-workflows/patterns.md - Common patterns
Or browse examples/ directory for .flow files.
Legacy Usage (Still Works)
Display the examples gallery for the Workflow Orchestration System.
Arguments: {{ARGS}}
Load and Display Examples
Primary Source: ~/.claude/plugins/repos/orchestration/docs/reference/examples.md - Curated examples documentation
Template Source: Use the Glob tool to list available example workflows:
Glob('~/.claude/plugins/repos/orchestration/examples/*.flow')
For each template found, read the file to extract its name and description from the YAML frontmatter.
Template Documentation: Reference ~/.claude/plugins/repos/orchestration/examples/README.md for detailed template information.
Display a formatted list combining both documentation examples and available templates to the user.
After Displaying Examples
Ask the user what they'd like to do next:
AskUserQuestion({
questions: [{
question: "What would you like to do with these examples?",
header: "Next",
multiSelect: false,
options: [
{label: "Try an example", description: "Execute one of these workflows"},
{label: "Learn more", description: "Get detailed docs on a topic"},
{label: "Create custom", description: "Build your own workflow"},
{label: "Return to menu", description: "Go back to main menu"}
]
}]
})
Handler Actions:
- Try an example → Prompt user to paste/specify which example syntax, then execute
/orchestration:run <syntax> - Learn more → Execute
/orchestration:explain - Create custom → Prompt for syntax and execute
/orchestration:run <syntax> - Return to menu → Execute
/orchestration: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.
- 2d ago First seen · 78 lines · 7 tokens per session scan A d3113ebc10c2
examples is a command published in the GitHub repository mbruhler/claude-orchestration (218 stars, last pushed 3mo ago), licensed MIT. It adds 7 tokens to every session and 549 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.