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/kavanaghpatrick/ralph-parallel/parallel-workflownpx skills add kavanaghpatrick/ralph-parallel --skill parallel-workflowgit clone --depth 1 https://github.com/kavanaghpatrick/ralph-parallelWhat 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 | $0.00068 | $0.03651 |
| Opus 5 | $0.00034 | $0.01826 |
| Sonnet 5 | $0.00014 | $0.00730 |
| Haiku 4.5 | $0.00007 | $0.00365 |
Grade A, and why
parallel-workflow 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 — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Workflow
Guides users through dispatching ralph-specum spec tasks for parallel execution via Claude Code Agent Teams.
Overview
Ralph Parallel extends ralph-specum by enabling multiple spec tasks to execute simultaneously across Agent Teams teammates. Instead of sequential task-by-task execution, tasks are partitioned into non-conflicting groups and dispatched to separate teammates.
Workflow
1. Create spec normally: /ralph-specum:start my-feature "goal"
2. Complete spec phases: research -> requirements -> design -> tasks
3. Dispatch for parallel: /ralph-parallel:dispatch
-> Analyzes tasks, partitions by file ownership, creates team, spawns teammates
-> Lead coordinates execution, runs verify checkpoints, handles serial tasks
4. Monitor progress: /ralph-parallel:status
5. Integrate results: /ralph-parallel:merge (worktree only; file-ownership auto-completes)
6. Handle remaining serial: /ralph-specum:implement (if any tasks remain)
Commands
| Command | Purpose | Key Flags |
|---|---|---|
/ralph-parallel:dispatch |
Analyze tasks, partition, create team, orchestrate | --max-teammates N, --strategy, --dry-run, --abort, --reclaim |
/ralph-parallel:status |
Show parallel execution progress | --json, --watch |
/ralph-parallel:merge |
Integrate results / verify consistency | --abort, --continue |
Strategies
File Ownership (Default)
Each teammate gets exclusive ownership of certain files. No merge needed -- teammates work in the same repo but on different files. The PreToolUse hook (file-ownership-guard.sh) enforces ownership at runtime by blocking writes to non-owned files.
Best for: Most projects. Simple, no merge complexity. Limitation: Tasks sharing files must be serialized.
Worktree
Each teammate gets its own git worktree with a separate branch. Full file access but requires merge step via /ralph-parallel:merge.
Best for: Highly coupled codebases where tasks touch overlapping files. Limitation: Merge conflicts possible, requires explicit merge step.
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 · 354 lines · 68 tokens per session scan A 3704fbbeeb96
parallel-workflow is a skill published in the GitHub repository kavanaghpatrick/ralph-parallel (7 stars, last pushed 5mo ago), licensed MIT. It adds 68 tokens to every session and 3,651 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
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…