execute-parallel

A command for having multiple coding agents implement the same plan in separate Git worktrees, which are isolated repository directories.

In plain words
What is it for?
Use it to run a plan across several parallel worktrees and collect each agent’s changes and results for comparison.
Why use it?
It lets you compare independent implementations of a feature while keeping each attempt separate for testing and review.

Command 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 commands/coleam00/context-engineering-intro/execute-parallel
Clone the repo
git clone --depth 1 https://github.com/coleam00/context-engineering-intro

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 273 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00273
Opus 5 $0.00000 $0.00137
Sonnet 5 $0.00000 $0.00055
Haiku 4.5 $0.00000 $0.00027

Measured 2d ago against content hash 9d20b321bd91, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

execute-parallel 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.

claude-code-full-guide/.claude/commands/execute-parallel.md · 27 lines

What it actually says

Parallel Task Version Execution

Variables

FEATURE_NAME: $ARGUMENTS PLAN_TO_EXECUTE: $ARGUMENTS NUMBER_OF_PARALLEL_WORKTREES: $ARGUMENTS

Instructions

We're going to create NUMBER_OF_PARALLEL_WORKTREES new subagents that use the Task tool to create N versions of the same feature in parallel.

Be sure to read PLAN_TO_EXECUTE.

This enables use to concurrently build the same feature in parallel so we can test and validate each subagent's changes in isolation then pick the best changes.

The first agent will run in trees/<FEATURE_NAME>-1/ The second agent will run in trees/<FEATURE_NAME>-2/ ... The last agent will run in trees/<FEATURE_NAME>-<NUMBER_OF_PARALLEL_WORKTREES>/

The code in trees/<FEATURE_NAME>-/ will be identical to the code in the current branch. It will be setup and ready for you to build the feature end to end.

Each agent will independently implement the engineering plan detailed in PLAN_TO_EXECUTE in their respective workspace.

When the subagent completes it's work, have the subagent to report their final changes made in a comprehensive RESULTS.md file at the root of their respective workspace.

Make sure agents don't run any tests or other code - focus on the code changes only.

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. 2d ago First seen · 27 lines · 0 tokens per session scan A 9d20b321bd91

Subscribe to this mod's changes

execute-parallel is a command published in the GitHub repository coleam00/context-engineering-intro (13,819 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 273 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-30.