Borrowing it
Nothing to install: this file belongs to KbWen/agentic-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/KbWen/agentic-os/main/.agents/skills/dispatching-parallel-agents/SKILL.mdgit clone --depth 1 https://github.com/KbWen/agentic-osWrote 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/agentic-os/dispatching-parallel-agents)<a href="https://agentmods.dev/skills/kbwen/agentic-os/dispatching-parallel-agents"><img src="https://agentmods.dev/badge/skills/kbwen/agentic-os/dispatching-parallel-agents/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kbwen/agentic-os/dispatching-parallel-agents"><img src="https://agentmods.dev/badge/skills/kbwen/agentic-os/dispatching-parallel-agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00336 |
| Opus 5.5 | $0.00012 | $0.00134 |
| Sonnet 5.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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- dispatching-parallel-agents — 100% identical, 0 lines differ
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.
- 1mo ago First seen · 42 lines · 29 tokens per session scan A 7d3c724ebab4
dispatching-parallel-agents is a skill published in the GitHub repository KbWen/agentic-os (220 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 336 once invoked, about $0.0001 per session on Opus 5.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
agent-config
Use when writing or editing agent configuration, especially permission rules in settings.json, skills, hooks, or MCP servers. Covers the permission-matching behaviour that makes a rule grant more than it reads, and how to check configuration with agentfile.
muster-frappe-metadata
Design, generate, review, apply, and roll back Frappe or ERPNext metadata changes through Muster. Use for DocTypes, child tables, custom fields, property setters, workflows, roles, permissions, reports, print formats, web pages, workspaces, fixtures, patches, or installed-app compatibility.
muster-frappe-release
Build, seed, deploy, break, measure, and prove a Muster Frappe release. Use for bench or site setup, migrations, realistic ERPNext data, role matrices, browser/mobile QA, performance and recovery tests, release evidence, Frappeverse demos, or normal-speed presentation video.
muster-frappe-security
Threat-model and negatively verify Muster integrations with Frappe OAuth, multi-tenancy, RBAC, field permissions, agent delegation, channels, secrets, approvals, and audit logs. Use for identity linking, site registration, Telegram onboarding, policy changes, permission tests, or security release gates.
muster-frappe-workflows
Design and implement durable multi-step Muster workflows for Frappe with agent, subagent, and nested task graphs. Use for workflow definitions, planning, delegation, tool policies, approvals, retries, schedules, triggers, artifacts, dynamic page creation, or Claude-style universal JS and JSON automation.
muster-frappe-orchestrator
Coordinate end-to-end Muster automation work across Frappe or ERPNext architecture, metadata, UI, workflows, security, testing, deployment, and evidence. Use for cross-cutting features, production plans, multi-agent delivery, or work that spans Muster core and a Frappe app.