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 skills add charlieviettq/awesome-agent-skill --skill dispatching-parallel-agentsgit clone --depth 1 https://github.com/charlieviettq/awesome-agent-skillWrote 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/charlieviettq/awesome-agent-skill/dispatching-parallel-agents)<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/dispatching-parallel-agents"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/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/charlieviettq/awesome-agent-skill/dispatching-parallel-agents"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/dispatching-parallel-agents.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.00430 |
| Opus 5 | $0.00018 | $0.00215 |
| Sonnet 5 | $0.00007 | $0.00086 |
| Haiku 4.5 | $0.00004 | $0.00043 |
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 9d 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.
What it actually says
Dispatching parallel agents
Gate (required)
Use this skill only if:
- User or parent explicitly allows parallel subagents, and
- Tasks are independent (no shared files, no ordering dependency on partial output)
If either condition fails, use sequential incremental-implementation instead.
When to use
- Independent reviews (security + tests + API contract) on the same commit
- Parallel research spikes with separate output files
- Large plan with disjoint file ownership per task
When not to use
- Single shared module being edited by multiple agents
- Database migrations or sequential deploy steps
- User did not approve multi-agent execution
Workflow
- Partition — list tasks with disjoint
Files:sets - Brief — each agent gets scope, constraints, verify command, output format
- Dispatch — run parallel agents; cap concurrency to what the harness supports
- Collect — gather outputs without assuming correctness
- Integrate — parent reconciles conflicts, runs full verification, single commit strategy per user rules
Integration checklist
- No conflicting edits to the same paths
- Combined diff reviewed by parent (or
requesting-code-review) - Full test/lint suite on integrated result
- User informed of what each agent did
Anti-patterns
- Parallel implementers on the same feature branch without file boundaries
- Merging subagent output without reading diffs
- Spawning agents to avoid reading the codebase
Related
subagent-driven-development, incremental-implementation, requesting-code-review, verify-before-done
Orchestration patterns inspired by obra/superpowers (MIT).
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.
- 9d ago First seen · 56 lines · 37 tokens per session scan A 82fd4bd83119
dispatching-parallel-agents is a skill published in the GitHub repository charlieviettq/awesome-agent-skill (26 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 430 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
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
phx-deps-update
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).
punch-list-manager
Digital punch list management for construction project closeout. Track deficiencies, assign corrections, photo documentation, and completion verification.
safety-inspection
Digital safety inspection system for construction sites. Checklists, hazard tracking, incident reporting, and compliance documentation.
data-evolution-analysis
Analyze data evolution patterns in construction organizations. Assess digital maturity and data strategy for construction companies.
data-silo-detection
Detect and map data silos in construction organizations. Identify disconnected data sources and integration opportunities.