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 agentmods add skills/jpoutrin/product-forge/parallel-setupnpx skills add jpoutrin/product-forge --skill parallel-setupgit 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-setup)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/parallel-setup"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/parallel-setup.svg" alt="Measured on agentmods" 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.00015 | $0.00879 |
| Opus 5 | $0.00008 | $0.00439 |
| Sonnet 5 | $0.00003 | $0.00176 |
| Haiku 4.5 | $0.00002 | $0.00088 |
Grade A, and why
parallel-setup 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
parallel-setup
Category: Parallel Development
Usage
/parallel-setup [--tech django|typescript|go]
Arguments
--tech: Optional - Technology stack hint for future decompositions (default: auto-detect)
Purpose
One-time initialization of the parallel/ directory at project root for parallel multi-agent development. This creates the infrastructure for organizing decomposed tasks by Tech Spec.
Run this once per project. Then use
/parallel-decomposefor each Tech Spec.
Execution Instructions for Claude Code
When this command is run, Claude Code should:
1. Create Directory Structure
mkdir -p parallel
Creates:
parallel/
├── README.md # Explains parallel development workflow
└── .gitignore # What to track vs ignore
2. Create README.md
Create parallel/README.md:
# Parallel Development Artifacts
This directory contains artifacts for parallel multi-agent development.
## Structure
Each Tech Spec decomposition creates a subdirectory:
parallel/ ├── TS-0042-inventory-system/ # Keyed by Tech Spec ID │ ├── manifest.json # Regeneration metadata │ ├── context.md # Shared project context │ ├── tasks/ # Task specifications │ ├── contracts/ # Shared types & API schema │ ├── prompts/ # Agent launch prompts │ ├── scripts/ # Launch & monitor scripts │ ├── architecture.md # System design │ └── task-graph.md # Dependency visualization └── ...
## Commands
- `/parallel-decompose <prd> --tech-spec <ts-file>` - Decompose PRD into tasks
- `/parallel-integrate --parallel-dir <dir>` - Verify integration
## Regeneration
Each subdirectory contains a `manifest.json` with metadata to regenerate artifacts:
```bash
# Re-run decomposition with same args
/parallel-decompose docs/prd.md --tech-spec tech-specs/approved/TS-XXXX.md
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.
- 2d ago First seen · 150 lines · 15 tokens per session scan A f8f32fc6c53b
parallel-setup is a skill published in the GitHub repository jpoutrin/product-forge (15 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 879 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…