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/dork-labs/dorkos/orchestrating-parallel-worknpx skills add dork-labs/dorkos --skill orchestrating-parallel-workgit clone --depth 1 https://github.com/dork-labs/dorkosWrote 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/dork-labs/dorkos/orchestrating-parallel-work)<a href="https://agentmods.dev/skills/dork-labs/dorkos/orchestrating-parallel-work"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/orchestrating-parallel-work.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.1 | $0.00043 | $0.01440 |
| Opus 5 | $0.00022 | $0.00720 |
| Sonnet 5 | $0.00009 | $0.00288 |
| Haiku 4.5 | $0.00004 | $0.00144 |
Grade A, and why
orchestrating-parallel-work 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 yesterday.
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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrating Parallel Work
Overview
This skill provides patterns for coordinating parallel subagent execution in Claude Code workflows. Apply these patterns when tasks can run simultaneously without interdependencies — parallel fan-out saves wall-clock time and keeps large intermediate output out of the main context.
When to Use
- Launching multiple research or exploration agents
- Implementing features with independent subtasks
- Running diagnostics that check multiple layers
- Processing batch operations with dependency graphs
- Any workflow where "wait for A, then start B" isn't required
Key Mechanics
The Agent tool spawns a subagent with its own isolated context:
- Parallel launch: to run agents concurrently, send multiple
Agentcalls in a single message. Each call takesdescription,prompt, andsubagent_type. - Results: the agent's final message comes back as the tool result. It is not shown to the user — relay what matters.
- Background mode:
run_in_background: truereturns immediately; the main conversation continues and completion arrives as an automatic task notification. No polling API exists — you are re-invoked when the agent finishes. - Follow-ups:
SendMessage(addressed by the agent's ID or name) continues a previously spawned agent with its context intact. A freshAgentcall starts from zero. - Isolation:
isolation: "worktree"gives an agent its own git worktree — required when parallel agents mutate tracked files.
Decision Logic
Should I Parallelize?
- Are tasks independent? → If no, use sequential
- Will each task take >30 seconds? → If no, sequential might be faster
- Do agents need each other's output? → If yes, use batched approach
- Will agents edit the same files? → If yes, must be sequential (or isolated worktrees)
Choosing the Pattern
| Situation | Pattern |
|---|---|
| 2-5 independent research/analysis tasks | Parallel Fan-Out |
| Many tasks with known dependencies | Dependency-Aware Batching |
| Long-running work alongside interactive work | Background Agents + Notify |
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.
- yesterday First seen · 138 lines · 43 tokens per session scan A 1f4208d63b6a
orchestrating-parallel-work is a skill published in the GitHub repository dork-labs/dorkos (9 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,440 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-09-03.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-pagerank-analyzer
Agent skill for pagerank-analyzer - invoke with $agent-pagerank-analyzer.
agent-neural-network
Agent skill for neural-network - invoke with $agent-neural-network.
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
openai-whisper-api
Transcribe audio via OpenAI Audio Transcriptions API (Whisper).