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.
npx skills add jpoutrin/product-forge --skill parallel-agentsgit clone --depth 1 https://github.com/jpoutrin/product-forgeWrote 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.
[](https://agentmods.dev/skills/jpoutrin/product-forge/parallel-agents)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/parallel-agents"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/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.
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/parallel-agents"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/parallel-agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00041 | $0.01732 |
| Opus 5.5 | $0.00016 | $0.00693 |
| Sonnet 5.5 | $0.00008 | $0.00346 |
| Haiku 4.5 | $0.00004 | $0.00173 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Agent Development
Orchestrate massively parallel development by decomposing work into independent tasks that multiple Claude Code instances can execute simultaneously.
CLI Tool: cpo (Claude Parallel Orchestrator)
The cpo CLI tool handles parallel agent execution with git worktree isolation.
Installation
pip install claude-parallel-orchestrator
# or
pipx install claude-parallel-orchestrator
cpo Commands
| Command | Description |
|---|---|
cpo init <dir> -t <tech-spec> -n <name> |
Initialize parallel directory |
cpo validate <dir> |
Validate manifest and structure |
cpo run <dir> |
Execute parallel agents |
cpo status <dir> |
Check execution status |
Workflow Overview
/parallel-setup -> One-time: creates parallel/ directory
|
/parallel-decompose -> Per Tech Spec: creates TS-XXXX-slug/ with all artifacts
|
/parallel-run -> Delegates to `cpo run` for execution
|
/parallel-integrate -> Verify & generate integration report
Directory Structure
Each decomposition creates an isolated artifact folder keyed by Tech Spec:
project/
parallel/ # Created by /parallel-setup (one-time)
README.md
.gitignore
TS-XXXX-{slug}/ # Created by /parallel-decompose
manifest.json # Regeneration metadata
context.md # Shared project context (token-efficient)
architecture.md # System design from Tech Spec
task-graph.md # Dependency visualization (Mermaid)
contracts/
types.py (or types.ts) # Shared domain types
api-schema.yaml # OpenAPI specification
tasks/
task-001-users.md # Compact YAML format
task-002-products.md
...
prompts/
agent-prompts.md # All launch commands
task-*.txt # Individual agent prompts
integration-report.md # Post-execution report
tech-specs/ # Source Tech Specs
approved/TS-XXXX-slug.md
CLAUDE.md # Project conventions
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 235 lines · 41 tokens per session scan A fc7444472022
parallel-agents is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 41 tokens to every session and 1,732 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.