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/kbwen/agent-virtual-office/dispatching-parallel-agentsnpx skills add KbWen/agent-virtual-office --skill dispatching-parallel-agentsgit clone --depth 1 https://github.com/KbWen/agent-virtual-officeWrote 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/kbwen/agent-virtual-office/dispatching-parallel-agents)<a href="https://agentmods.dev/skills/kbwen/agent-virtual-office/dispatching-parallel-agents"><img src="https://agentmods.dev/badge/skills/kbwen/agent-virtual-office/dispatching-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.00029 | $0.00336 |
| Opus 5 | $0.00015 | $0.00168 |
| Sonnet 5 | $0.00006 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00034 |
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 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.
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.
This is a copy
100% identical to dispatching-parallel-agents — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Dispatching Parallel Agents
Overview
Parallel agents are suitable for handling splittable tasks with low coupling. The goal is to shorten total lead time, not to increase coordination overhead.
When to Use
- Tasks can be decomposed into independent sub-problems (e.g., documentation, testing, separate modules).
- Dependencies between sub-tasks are low; clear interfaces can be defined.
- Deadlines are tight, and lead time needs compression.
When NOT to Use
- Problems are highly coupled and require frequent synchronization.
- Requirements are still unclear; the cost of decomposition outweighs the benefits.
- Unable to define unified acceptance criteria.
Four-Step Pattern
- Decompose: Split into mutually exclusive, independently verifiable sub-tasks.
- Dispatch: Specify each agent's scope, inputs/outputs, constraints, and deadline.
- Sync: Perform brief synchronizations at fixed checkpoints to handle conflicts and dependencies.
- Merge: Integrate outputs using a unified set of acceptance criteria and run regression tests.
Best Practices
- Every sub-task MUST have a clear Definition of Done.
- Collaborate primarily via interface contracts to avoid modifying each other's blocks.
- Perform a global check before final integration.
Common Mistakes
- Forcefully splitting non-splittable tasks, leading to rework.
- Lacking sync checkpoints, resulting in integration explosion at the end.
- Sub-tasks passing individually but failing global acceptance.
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.
- 4d ago First seen · 42 lines · 29 tokens per session scan A 7d3c724ebab4
dispatching-parallel-agents is a skill published in the GitHub repository KbWen/agent-virtual-office (16 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 336 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to dispatching-parallel-agents, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
frame-macos-notification
拟真 macOS 通知 banner + app icon + 标题正文, 适合 video overlay / 产品发布预告.
prototype-web
可点击的功能性 Web 原型, 含导航、英雄区、特性区、CTA.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
deck-pitch
10 页融资 deck, 白底 + 蓝紫渐变 hero, traction 柱状, $X.XM ask.
waitlist-page
【模板: 等候名单页 / Waitlist】 【意图】为新产品 / 早鸟内测做一张极简等候页。 【布局】.
argent-tv-interact
Control and inspect TV apps via argent — Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…