parallel-run

parallel-run is a skill for Claude Code from jpoutrin/product-forge. It costs 13 tokens per session (1,462 once invoked), scanned A, original, MIT.

A command for running development tasks in parallel through separate Git worktrees. It validates the task directory, starts the assigned agents, monitors their work, and reports the results.

In plain words
What is it for?
Use it to validate a parallel-task directory, execute its agent tasks, or view the current execution status.
Why use it?
It coordinates multiple coding tasks while keeping their file changes separated and checking that the setup is usable first.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions Claude Code.

Part of the product-design plugin — 43 skills, 8 agents shipped together

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 skills/jpoutrin/product-forge/parallel-run
Any agent
npx skills add jpoutrin/product-forge --skill parallel-run
Clone the repo
git clone --depth 1 https://github.com/jpoutrin/product-forge

Made for: Claude Code.

Or install product-design, the plugin that ships this one along with the rest of its 43 skills, 8 agents.

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 parallel-run

README.md
[![agentmods](https://agentmods.dev/badge/skills/jpoutrin/product-forge/parallel-run.svg)](https://agentmods.dev/skills/jpoutrin/product-forge/parallel-run)
Your own site
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/parallel-run"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/parallel-run.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,462 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.1 $0.00013 $0.01462
Opus 5 $0.00006 $0.00731
Sonnet 5 $0.00003 $0.00292
Haiku 4.5 $0.00001 $0.00146

Measured 2d ago against content hash 450d80171a3e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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

plugins/product-design/skills/parallel-run/SKILL.md · 255 lines

How it starts

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

parallel-run

Category: Parallel Development

Usage

/parallel-run <parallel-dir> [options]

Arguments

  • <parallel-dir>: Required - Path to decomposed parallel folder (e.g., parallel/TS-0042-inventory/)
  • --validate: Only validate the directory without executing
  • --status: Show current execution status

Purpose

Execute parallel agent development tasks using the cpo (Claude Parallel Orchestrator) CLI tool. This command:

  1. Validates the parallel directory and manifest.json
  2. Executes parallel agents using git worktrees
  3. Monitors progress and reports results

Prerequisites

  • Run /parallel-decompose first (creates tasks, prompts, manifest.json)
  • cpo tool installed: pip install claude-parallel-orchestrator or pipx install claude-parallel-orchestrator
  • Git working tree is clean (no uncommitted changes)
  • Claude Code CLI available: claude --version

Execution Instructions for Claude Code

When this command is run, Claude Code should delegate to the cpo CLI tool.

0. Parse Arguments

Extract from user input:

  • PARALLEL_DIR: The parallel directory path
  • VALIDATE_ONLY: Boolean, true if --validate specified
  • STATUS_ONLY: Boolean, true if --status specified

1. Check cpo Tool Availability

cpo --help

If cpo is not installed, display:

ERROR: cpo (Claude Parallel Orchestrator) not found

Install with:
  pip install claude-parallel-orchestrator
  # or
  pipx install claude-parallel-orchestrator

Documentation: https://github.com/jpoutrin/claude-parallel-orchestrator

2. Handle --validate Option

If --validate is specified:

cpo validate "$PARALLEL_DIR"

Display the validation output and stop.

3. Handle --status Option

If --status is specified:

cpo status "$PARALLEL_DIR"

Display the status output and stop.

4. Run Parallel Execution

For default execution (no special flags):

cpo run "$PARALLEL_DIR"

The cpo run command will:

  1. Validate the manifest.json
  2. Create git worktrees for each task
  3. Launch Claude agents in parallel (respecting wave dependencies)
  4. Monitor progress and handle failures
  5. Generate execution logs in $PARALLEL_DIR/logs/
  6. Create final report in $PARALLEL_DIR/report.json

Read the full file on GitHub · 255 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. 2d ago First seen · 255 lines · 13 tokens per session scan A 450d80171a3e

Subscribe to this mod's changes

parallel-run is a skill published in the GitHub repository jpoutrin/product-forge (15 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 1,462 once invoked, about $0.0001 per session on Opus 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-09-03.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 95 tokens