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 epic-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/epic-ship)<a href="https://agentmods.dev/skills/davidtheproduct/claude-ship-skills/epic-ship"><img src="https://agentmods.dev/badge/skills/davidtheproduct/claude-ship-skills/epic-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/epic-ship"><img src="https://agentmods.dev/badge/skills/davidtheproduct/claude-ship-skills/epic-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.00099 | $0.01583 |
| Opus 5 | $0.00049 | $0.00792 |
| Sonnet 5 | $0.00020 | $0.00317 |
| Haiku 4.5 | $0.00010 | $0.00158 |
Grade A, and why
epic-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 11d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Epic Ship
Runs a multi-phase epic (a markdown plan doc with a phase list, e.g. docs/epics/epic-<n>.md) phase by phase, calling the ship-pr skill once per phase for the actual worktree/implement/verify/PR/merge/cleanup mechanics, until every phase is shipped or you hit an explicit review checkpoint. This is the sequential composition operator of the ship stack: parallel-ship fans out when changes are independent; this skill loops when phase N+1 builds on phase N's code.
The default failure mode this skill exists to fix is stalling after a routine merge waiting to be told to continue. ship-pr ships one PR and stops - epic-ship is what decides to call it again immediately.
Step 0: Reconcile against reality first
Before touching anything:
git statusandgit branch --show-currentat the repo root - confirm it's on the default branch and clean. If not clean and the changes aren't yours, stop and tell the user.git worktree list- confirm no stray worktree already covers this epic's phases.- Read the epic doc fully: phase list, current status column, and any explicit checkpoint markers (see Step 3).
gh pr list --search "<epic keyword>" --state allandgit log --oneline -20- confirm what's actually already merged before trusting the epic doc's status table. Epic docs drift; git and GitHub are the source of truth. This step exists because past sessions have reported phases as unshipped when they'd already landed, or vice versa - always reconcile before planning work.
Step 1: Plan the run
List the unshipped phases in order. For each, note what it touches (which packages/apps - and which specialized subagent fits, if the project defines any) and whether it's DB/migration work (regenerate types afterward if the project has a typegen step).
Then re-order for risk, not just dependency
Epic docs number phases in dependency order (DB -> backend -> frontend). That is not always a safe merge order. Before shipping anything, ask of each phase:
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.
- 11d ago First seen · 85 lines · 99 tokens per session scan A be5c57be3323
epic-ship is a skill published in the GitHub repository davidtheproduct/claude-ship-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 1,583 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.
standup-summary
Generate a standup or weekly-review update from actual work evidence - commits, branches, PRs, and issues across one or more repositories - grouped into done / in progress / blocked / next, written in plain human sentences rather than commit-message-speak. Use when preparing a daily standup, a weekly review, a sprint…