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 skills/mbruhler/claude-orchestration/creating-workflowsnpx skills add mbruhler/claude-orchestration --skill creating-workflowsgit 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/skills/mbruhler/claude-orchestration/creating-workflows)<a href="https://agentmods.dev/skills/mbruhler/claude-orchestration/creating-workflows"><img src="https://agentmods.dev/badge/skills/mbruhler/claude-orchestration/creating-workflows.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.00065 | $0.02847 |
| Opus 5 | $0.00032 | $0.01424 |
| Sonnet 5 | $0.00013 | $0.00569 |
| Haiku 4.5 | $0.00006 | $0.00285 |
Grade C, and why
orchestration:creating-workflows 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 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.
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 — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Orchestration Workflows
I'll help you create powerful orchestration workflows that coordinate multiple Claude Code agents. I use Socratic questioning to understand your needs and generate optimal workflow syntax.
When I Activate
I automatically activate when you:
- Describe a multi-step process you want to automate
- Mention "workflow", "orchestration", "automate", "coordinate agents"
- Ask "how do I create a workflow?"
- Want to connect multiple agents or tasks
- Ask about automating repetitive processes
My Process
1. Understanding Your Intent
CRITICAL: I use AskUserQuestion tool for ALL questions. NO plain text numbered lists.
I'll ask strategic questions to understand:
- What problem you're solving
- What your goal is
- What scope you have in mind
- What external data sources you need (APIs, web scraping, databases)
2. Detecting Temp Script Needs
I automatically scan for these triggers:
- External APIs: Reddit, Twitter, GitHub, ProductHunt, etc.
- Web Scraping: Extracting data from websites
- Data Processing: Analyzing 10+ items, statistical analysis
- Authentication: Any service requiring API keys
If detected → I'll proactively create temp scripts for you
3. Identifying the Pattern
I'll determine if your workflow is:
- Sequential: One step after another (
->) - Parallel: Multiple tasks at once (
||) - Conditional: Based on results (
~>) - Semantic Routing: Dynamic switch statements based on LLM interpretation (
route() =>) - Scheduled: Runs automatically in the background (
@schedule(...)) - Hybrid: Combination of above
3. Designing the Workflow
I'll help you define:
- Which agents to use (built-in or custom)
- How data flows between steps
- Error handling strategy
- Review checkpoints
4. Generating Syntax
I'll create clean, readable workflow syntax like:
# Simple sequential workflow
explore:"Analyze codebase" ->
implement:"Add feature" ->
test:"Run tests"
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 396 lines · 65 tokens per session scan C e5d75a81189a
orchestration:creating-workflows is a skill published in the GitHub repository mbruhler/claude-orchestration (218 stars, last pushed 3mo ago), licensed MIT. It adds 65 tokens to every session and 2,847 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…