agent-spawning

A guide to running separate Claude Code agents for tasks such as research, coding, and testing. It explains how to start those agents together and use coordination tools only to organize them.

In plain words
What is it for?
Use it when planning multi-agent work, assigning roles, starting agents concurrently, and coordinating their results.
Why use it?
It helps avoid running agent work in the wrong way or one task at a time when several independent tasks can proceed together.

Agent for Claude Code

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.

agentmods
npx agentmods add agents/earthmanweb/claude-flow-plugin/agent-spawning
Clone the repo
git clone --depth 1 https://github.com/EarthmanWeb/claude-flow-plugin

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 175 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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 $0.00000 $0.00175
Opus 5 $0.00000 $0.00088
Sonnet 5 $0.00000 $0.00035
Haiku 4.5 $0.00000 $0.00017

Measured yesterday against content hash 74bfe922137a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agent-spawning 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 yesterday.

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.

Origin

This is a copy

100% identical to agent-spawning — 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.

.claude/commands/agents/agent-spawning.md · 29 lines

What it actually says

agent-spawning

Guide to spawning agents with Claude Code's Task tool.

Using Claude Code's Task Tool

CRITICAL: Always use Claude Code's Task tool for actual agent execution:

// Spawn ALL agents in ONE message
Task("Researcher", "Analyze requirements...", "researcher")
Task("Coder", "Implement features...", "coder")
Task("Tester", "Create tests...", "tester")

MCP Coordination Setup (Optional)

MCP tools are ONLY for coordination:

mcp__claude-flow__swarm_init { topology: "mesh" }
mcp__claude-flow__agent_spawn { type: "researcher" }

Best Practices

  1. Always spawn agents concurrently
  2. Use Task tool for execution
  3. MCP only for coordination
  4. Batch all operations
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. yesterday First seen · 29 lines · 0 tokens per session scan A 74bfe922137a

Subscribe to this mod's changes

agent-spawning is an agent published in the GitHub repository EarthmanWeb/claude-flow-plugin (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 175 tokens. A static security scan graded it A with 0 findings. It is 100% identical to agent-spawning, differing in 0 lines, and is treated as a copy.