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/mtnyilmaz/agents/workflow-parallel-agentsnpx skills add mtnyilmaz/agents --skill workflow-parallel-agentsgit clone --depth 1 https://github.com/mtnyilmaz/agentsWrote 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/mtnyilmaz/agents/workflow-parallel-agents)<a href="https://agentmods.dev/skills/mtnyilmaz/agents/workflow-parallel-agents"><img src="https://agentmods.dev/badge/skills/mtnyilmaz/agents/workflow-parallel-agents.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.00044 | $0.01949 |
| Opus 5 | $0.00022 | $0.00975 |
| Sonnet 5 | $0.00009 | $0.00390 |
| Haiku 4.5 | $0.00004 | $0.00195 |
Grade A, and why
dispatching-parallel-agents 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dispatching Parallel Agents
Overview
When you have multiple independent problems — different failing test files, different broken subsystems, different bugs — investigating them sequentially wastes wall-clock time. Each investigation is independent, so each can happen concurrently in its own subagent.
Core principle: One subagent per independent problem domain. Let them work in parallel. Integrate at the end.
Distinct from workflow-subagent-driven: That skill executes a plan serially (one task at a time) because plan tasks typically share files. This skill runs investigations concurrently because the problems are disjoint.
When to Use
- 3+ test files failing with clearly unrelated root causes
- Multiple subsystems broken independently (e.g. auth + billing + email)
- Independent code audits (e.g. run all SAST skills at once)
- Parallel documentation / dependency upgrades across unrelated modules
- Each problem can be understood and fixed without state from the others
When NOT to use:
- Failures look related — fixing one might fix the others (investigate together first)
- You need full-system context to understand what's broken
- Exploratory debugging — you don't yet know what the problem is
- Subagents would touch the same files (they will conflict)
┌─ Multiple problems?
│ │
│ ▼
│ Independent? ──── no ── Single investigation, sequential
│ │
│ yes
│ │
│ ▼
│ Shared files? ──── yes ── Sequential subagents (avoid conflicts)
│ │
│ no
│ │
│ ▼
└──→ PARALLEL DISPATCH
The Workflow
1. Identify independent domains
2. Build one focused prompt per domain
3. Dispatch all subagents in the same message (parallel)
4. Collect returns
5. Verify no file-level conflicts
6. Run the full suite
7. Integrate
What ships with it
1 file 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.
- 3d ago First seen · 221 lines · 44 tokens per session scan A 76222cf516dc
dispatching-parallel-agents is a skill published in the GitHub repository mtnyilmaz/agents (6 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 1,949 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-31.
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…