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/debugging-workflowsnpx skills add mbruhler/claude-orchestration --skill debugging-workflowsgit 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.00039 | $0.00926 |
| Opus 5 | $0.00019 | $0.00463 |
| Sonnet 5 | $0.00008 | $0.00185 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
debugging-workflows 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging Orchestration Workflows
I help diagnose and fix workflow execution issues using systematic debugging techniques.
When I Activate
I activate when you:
- Experience workflow failures
- Get syntax errors
- Have agent execution issues
- Variables not working as expected
- Ask "why isn't this working?"
Common Issues
Syntax Errors
Problem: Workflow won't parse
Symptoms:
- "Unexpected token" errors
- "Invalid syntax" messages
- Workflow won't start
Solutions:
- Check operator syntax:
->,||,~>(not=>or&&) - Verify bracket matching:
[...] - Check quote matching:
"instruction" - Validate agent names (no typos)
Agent Not Found
Problem: Agent reference doesn't resolve
Symptoms:
- "Agent 'X' not found"
- Execution stops at agent invocation
Solutions:
- Check spelling of agent name
- Verify temp agent file exists:
temp-agents/agent-name.md - Check defined agent in registry:
agents/registry.json - Ensure built-in agent name is correct
Variable Issues
Problem: Variables not passing correctly
Symptoms:
{variable}shows as literal text- "Variable not found" errors
- Empty variable values
Solutions:
- Verify capture syntax:
agent:"task":variable_name - Check interpolation:
"Use {variable_name}" - Ensure variable set before use
- Check variable name spelling
Parallel Execution Failures
Problem: Parallel tasks failing or hanging
Symptoms:
- Only some parallel tasks complete
- Workflow hangs at parallel section
- Inconsistent results
Solutions:
- Ensure tasks are independent (no shared state)
- Check syntax:
[task1 || task2 || task3] - Verify each task can run standalone
- Check for race conditions
Checkpoint Issues
Problem: Checkpoints not triggering
Symptoms:
- Checkpoints skipped
- No user prompt shown
- Workflow continues without pause
Solutions:
- Check checkpoint syntax:
@checkpoint-name - Verify not in auto-mode
- Ensure checkpoint is reachable in flow
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 · 173 lines · 39 tokens per session scan A 87df54d3ed32
debugging-workflows is a skill published in the GitHub repository mbruhler/claude-orchestration (218 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 926 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…