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/jpm1118/threadwork/dispatching-parallel-agentsnpx skills add JPM1118/Threadwork --skill dispatching-parallel-agentsgit clone --depth 1 https://github.com/JPM1118/ThreadworkWhat 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.00000 | $0.01979 |
| Opus 5 | $0.00000 | $0.00989 |
| Sonnet 5 | $0.00000 | $0.00396 |
| Haiku 4.5 | $0.00000 | $0.00198 |
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 2d 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dispatching Parallel Agents Skill
Resolve multiple independent problems concurrently by deploying separate agents to different failure domains.
Core Principle
PARALLELIZE INDEPENDENT WORK
If problems don't share state or dependencies, solve them simultaneously.
When to Use This Skill
Use parallel agents when:
- You have 3+ independent failures (tests, bugs, tasks)
- Problems are in different areas of the codebase
- Agents can work without shared state
- You want to accelerate multi-issue resolution
When NOT to Use This Skill
Don't parallelize when:
- Problems share state or files
- One problem's fix might affect another
- Problems are in the same module
- Sequential execution provides important context
Prerequisites
- Clear problem decomposition
- Verified problem independence
- Specific scope for each agent
- Conflict detection plan
The Parallel Dispatch Process
┌─────────────────────────────────────────────────────────────┐
│ Parallel Agent Dispatch Flow │
├─────────────────────────────────────────────────────────────┤
│ │
│ Step 1: DECOMPOSE │
│ ↓ Identify independent problems │
│ │
│ Step 2: VERIFY INDEPENDENCE │
│ ↓ Confirm no shared state/files │
│ │
│ Step 3: SCOPE EACH AGENT │
│ ↓ Narrow task, specific context, clear objective │
│ │
│ Step 4: DISPATCH ALL │
│ ↓ Launch simultaneously (not sequentially) │
│ │
│ Step 5: COLLECT RESULTS │
│ ↓ Gather completion reports │
│ │
│ Step 6: INTEGRATE │
│ Verify no conflicts, validate full suite │
│ │
└─────────────────────────────────────────────────────────────┘
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.
- 2d ago First seen · 319 lines · 0 tokens per session scan A b9c9d285b42d
dispatching-parallel-agents is a skill published in the GitHub repository JPM1118/Threadwork (5 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,979 tokens. 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…