prep-parallel

A command for creating several Git worktrees, which are separate working directories connected to the same repository, for one feature.

In plain words
What is it for?
Use it to create numbered branches and worktree folders, then verify that each directory was created correctly.
Why use it?
It prepares isolated directories so multiple coding agents can work on the same feature in parallel without modifying the same files directly.

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/prep-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 132 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.00132
Opus 5 $0.00000 $0.00066
Sonnet 5 $0.00000 $0.00026
Haiku 4.5 $0.00000 $0.00013

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

Security

Grade A, and why

prep-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/prep-parallel.md · 14 lines

What it actually says

Initialize parallel git worktree directories for parallel Claude Code agents

Variables

FEATURE_NAME: $ARGUMENTS NUMBER_OF_PARALLEL_WORKTREES: $ARGUMENTS

Execute these commands

Execute the loop in parallel with the Batch and Task tool

  • create a new dir trees/
  • for i in NUMBER_OF_PARALLEL_WORKTREES
    • RUN git worktree add -b FEATURE_NAME-i ./trees/FEATURE_NAME-i
    • RUN cd trees/FEATURE_NAME-i, git ls-files to validate
  • RUN git worktree list to verify all trees were created properly
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 · 14 lines · 0 tokens per session scan A 2b63fed5ab0a

Subscribe to this mod's changes

prep-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 132 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.