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/rungit 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/run)<a href="https://agentmods.dev/commands/mbruhler/claude-orchestration/run"><img src="https://agentmods.dev/badge/commands/mbruhler/claude-orchestration/run.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.04738 |
| Opus 5 | $0.00003 | $0.02369 |
| Sonnet 5 | $0.00001 | $0.00948 |
| Haiku 4.5 | $0.00001 | $0.00474 |
Grade C, and why
run scanned grade C with 1 finding 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ./temp-scripts/* How it starts
The opening of the file, as written. The whole thing — 653 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ DEPRECATED: Orchestration Workflow Execution
This command is deprecated. Use the executing-workflows skill instead for better visualization, error handling, and progress tracking.
The skill automatically activates when you provide workflow syntax or ask to run a workflow.
Migration Guide
Instead of: /orchestration:run step1 -> step2 -> step3
Just provide syntax:
step1:"task" -> step2:"task" -> step3:"task"
The executing-workflows skill will automatically activate and execute with full visualization and steering support.
Legacy Usage (Still Works)
Parse and execute a workflow defined using orchestration syntax.
Arguments: {{ARGS}}
The workflow to execute. Can be provided in two formats:
- Raw syntax - Direct workflow operators (e.g.,
step1 -> step2) - Template format - YAML frontmatter with
workflowand optionalvisualizationfields
Execution Phases
Phase -1: Template Detection (if applicable)
Check for YAML frontmatter:
If input starts with ---, it's a template with frontmatter:
if (input.startsWith('---')) {
const { frontmatter, content } = parseYAMLFrontmatter(input)
// Extract fields
const visualization = frontmatter.visualization // Static ASCII art
const workflow = frontmatter.workflow // Raw workflow syntax
// Use workflow syntax from frontmatter, not content after ---
syntax = workflow
// Store visualization for Phase 2
staticVisualization = visualization
}
If no frontmatter detected, use input as-is for raw syntax.
Phase 0: Pre-Parse (Temporary Agents)
Reference: ${CLAUDE_PLUGIN_ROOT}/docs/features/temporary-agents.md
Registry: ./temp-agents/ (in current working directory)
If workflow contains temporary agent syntax ($agent-name):
- Extract Definitions - Find
$name := {...}patternsconst { registry, cleanedSyntax } = extractTempAgentDefinitions(syntax)
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.
- 4d ago First seen · 653 lines · 6 tokens per session scan C 1a0f415f31a6
run 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 4,738 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.