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 davidtheproduct/claude-ship-skills --skill parallel-shipgit clone --depth 1 https://github.com/davidtheproduct/claude-ship-skillsWrote 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/davidtheproduct/claude-ship-skills/parallel-ship)<a href="https://agentmods.dev/skills/davidtheproduct/claude-ship-skills/parallel-ship"><img src="https://agentmods.dev/badge/skills/davidtheproduct/claude-ship-skills/parallel-ship/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/davidtheproduct/claude-ship-skills/parallel-ship"><img src="https://agentmods.dev/badge/skills/davidtheproduct/claude-ship-skills/parallel-ship.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.00090 | $0.01068 |
| Opus 5 | $0.00045 | $0.00534 |
| Sonnet 5 | $0.00018 | $0.00214 |
| Haiku 4.5 | $0.00009 | $0.00107 |
Grade A, and why
parallel-ship 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 12d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Ship
Coordinate several PR-sized changes at once by launching background agents from the session that did the analysis, keeping high-risk changes (payments, auth, anything that shouldn't self-merge) in the main session.
This is the chairperson pattern in its parallel form: the session that did the analysis is the only one holding the verified facts, so it stays in charge - writing complete briefs for disposable worker agents, judging their reports against context only it holds - rather than handing off a lossy summary to fresh sessions.
When to use
- One analysis/design context has produced 3+ shippable changes.
- The changes touch disjoint files (check before launching; two agents on the same file = merge conflicts).
- The spec for each change is concrete enough to write down (file paths, exact behavior, verification commands). If you cannot write the spec, the analysis is not finished - do not launch.
When NOT to use: sequential phases where PR N+1 builds on PR N's code (use epic-ship), or a single change (use ship-pr).
Workflow
- Carve the work into PRs by file/module boundary. One worktree per PR, all forked from the same base via
bash ~/.claude/skills/ship-pr/scripts/worktree-new.sh <branch>(never stacked - each agent starts from the remote default branch, not from another agent's branch). - Split by risk, not by size.
- Mechanical/well-specified changes (new components, sweeps, copy, config) -> background agents, cheaper model is fine.
- High-risk changes (payments, auth, data-integrity, anything that shouldn't self-merge) -> the MAIN session implements these itself, and they don't auto-merge even on green CI.
- Write self-contained agent specs. Each agent prompt must include: worktree setup (via
ship-pr'sworktree-new.sh, never edit the base checkout directly), exact file targets, any project-specific copy/style rules, verification commands (build/typecheck/test - fresh, not cached), commit message format, and "open PR with a DO NOT MERGE line, do not merge, do not close the worktree, return PR URL + decisions made." - Launch disjoint agents in parallel; implement the risky PRs yourself while they run.
- Review each agent's report against your context - you hold the verified facts from the analysis pass, so judgment calls the agents made (placement, naming, edge cases) are cheap to check against it.
- Preview round: all PRs sit unmerged with preview links or
gh pr diff. Relay feedback by resuming the same agents (they keep their worktree and context) rather than starting fresh ones. - Merge in dependency order on the user's go,
gh pr merge --squash --delete-branch, then close every worktree viaship-pr'sworktree-close.sh.
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.
- 12d ago First seen · 44 lines · 90 tokens per session scan A b1bc75379353
parallel-ship is a skill published in the GitHub repository davidtheproduct/claude-ship-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 1,068 once invoked, about $0.0005 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
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".
work-on-ticket
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKETID]" or similar phrases.
git-flow
Use when committing, branching, opening PRs, or deciding merge/branch strategy.
get-up-to-speed
Reviews the latest git history, branch state, Linear ticket, and open work to build a concise situational summary. Use when picking up work after another agent, resuming a session, or onboarding to a branch mid-flight.