dispatching-parallel-agents

dispatching-parallel-agents is a skill for Claude Code, Codex from EvoClaw/amplify. It costs 28 tokens per session (1,716 once invoked), scanned A, original, MIT.

A workflow for assigning separate AI agents to independent experiments or tasks that can run without shared state or ordering dependencies.

In plain words
What is it for?
It helps decide whether tasks are independent, choose between parallel and sequential work, and coordinate one agent per independent task.
Why use it?
It reduces waiting when multiple unrelated pieces of work can be completed at the same time.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit It helps decide whether tasks are independent, choose between parallel and sequential work, and coordinate one agent per independent task.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/evoclaw/amplify/dispatching-parallel-agents
Install

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.

Any agent
npx skills add EvoClaw/amplify --skill dispatching-parallel-agents
Clone the repo
git clone --depth 1 https://github.com/EvoClaw/amplify

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for dispatching-parallel-agents

README.md
[![agentmods](https://agentmods.dev/badge/skills/evoclaw/amplify/dispatching-parallel-agents/github.svg)](https://agentmods.dev/skills/evoclaw/amplify/dispatching-parallel-agents)
Your own site
<a href="https://agentmods.dev/skills/evoclaw/amplify/dispatching-parallel-agents"><img src="https://agentmods.dev/badge/skills/evoclaw/amplify/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.

agentmods 80×15 button for dispatching-parallel-agents

Your own site · 80×15
<a href="https://agentmods.dev/skills/evoclaw/amplify/dispatching-parallel-agents"><img src="https://agentmods.dev/badge/skills/evoclaw/amplify/dispatching-parallel-agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,716 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.01716
Opus 5.5 $0.00011 $0.00686
Sonnet 5.5 $0.00006 $0.00343
Haiku 4.5 $0.00003 $0.00172

Measured 1mo ago against content hash 91a20c3fe250, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

skills/dispatching-parallel-agents/SKILL.md · 212 lines

How it starts

The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dispatching Parallel Agents

Overview

When you have multiple independent experiments (different datasets, different methods, different baselines), running them sequentially wastes time. Each experiment is independent and can happen in parallel.

Core principle: Dispatch one agent per independent problem domain. Let them work concurrently.

Use this skill alongside:

  • amplify:experiment-execution for Phase 4 orchestration
  • amplify:results-verification-protocol before claiming completion
  • amplify:results-integration when consolidating outputs

When to Use

digraph when_to_use {
    "Multiple experiments?" [shape=diamond];
    "Are they independent?" [shape=diamond];
    "Single agent runs all" [shape=box];
    "One agent per experiment" [shape=box];
    "Can they work in parallel?" [shape=diamond];
    "Sequential agents" [shape=box];
    "Parallel dispatch" [shape=box];

    "Multiple experiments?" -> "Are they independent?" [label="yes"];
    "Are they independent?" -> "Single agent runs all" [label="no - related"];
    "Are they independent?" -> "Can they work in parallel?" [label="yes"];
    "Can they work in parallel?" -> "Parallel dispatch" [label="yes"];
    "Can they work in parallel?" -> "Sequential agents" [label="no - shared state"];
}

Use when:

  • 3 independent experiments on different datasets
  • Multiple baseline implementations to evaluate
  • Each experiment can be understood without context from others
  • No shared state between experiments

Don't use when:

  • Experiments are related (result of one informs another)
  • Need to understand full system state
  • Agents would interfere with each other

The Pattern

1. Identify Independent Domains

Group experiments by what they investigate:

  • Experiment A: Baseline model on dataset X
  • Experiment B: Proposed method on dataset Y
  • Experiment C: Ablation study on component Z

Each domain is independent - running the baseline doesn't affect the ablation study.

2. Create Focused Agent Tasks

Read the full file on GitHub · 212 lines

Changes

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.

  1. 1mo ago First seen · 212 lines · 28 tokens per session scan A 91a20c3fe250

Subscribe to this mod's changes

dispatching-parallel-agents is a skill published in the GitHub repository EvoClaw/amplify (11 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 1,716 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.