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 bendrucker/claude --skill shipgit clone --depth 1 https://github.com/bendrucker/claudeWrote 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/bendrucker/claude/ship)<a href="https://agentmods.dev/skills/bendrucker/claude/ship"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/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/bendrucker/claude/ship"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.02009 |
| Opus 5 | $0.00020 | $0.01005 |
| Sonnet 5 | $0.00008 | $0.00402 |
| Haiku 4.5 | $0.00004 | $0.00201 |
Grade A, and why
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 yesterday.
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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship
Gate review passes on the diff, run them in order, open the PR, babysit CI to green, refresh the body from a clean context. Each pass fans out on its own; ship only gates and orders.
Default end state green and ready: CI green, bot comments triaged, body refreshed, stopped for your web review. --merge drives to merged.
Context
- Working tree: !
git status --short
Decide What Applies
Resolve the base to a remote ref so ship's view matches what the PR merges against. From the base branch (default main, or --base <parent> on a stack), take its tracking ref via git rev-parse --abbrev-ref --symbolic-full-name <base>@{u}, falling back to origin/<base>. Fetch it first (git fetch) so a stale local <base> never inflates the diff with already-merged commits. Diff git diff <resolved>...HEAD, plus a plain git diff for uncommitted work, and thread the resolved ref as --base to every gated pass (including review:code). Gate each pass on the file set, its size, and the content behind any judgment call (new comments, refactor or new behavior). Full matrix and heuristics: references/passes.md.
plan:review: a substantial approved plan is in context (~/.claude/plans/file) and the session ran long or redirected enough that the diff could have drifted from it. Skip otherwise (full gate).- Correctness and quality: code changed. Exactly one of
review:code <effort> --fix(default) orsimplify(pure refactor, no new behavior). Skip on docs/config-only. comments:audit: diff adds code comments.pull-request:follow-up --local: a supported review bot is available for the repo and the diff clears the Bot Review Gate. Runs the hosted reviewer locally before the PR exists.github:copilot: code changed on a repo I own and the diff clears the Cross-Model Gate. A second model reads the diff before the PR exists.writing:review: diff touches prose (.md,.mdx,.rst, docs).run: diff has a runtime surface. Drive the change in the real app, not just tests. Skip on docs-only and tests-only.review:human: always on. Ben reads the cleaned diff last, for architecture and slop.--skip humandrops it, and passes--no-review-bodythrough to create.
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.
- yesterday Changed · +6 lines 2ae638a9dc11
- 6d ago Changed 7e8dd06781a6
- 9d ago First seen · 101 lines · 41 tokens per session scan A 1ff3ee8f3f8a
ship is a skill published in the GitHub repository bendrucker/claude (16 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 2,009 once invoked, about $0.0002 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
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
han-release
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…
release-docs
Diff-driven documentation sync after a release. Determines what source files changed, delegates changelog to zuvo:docs, updates only docs whose source changed. Flags: --dry-run, explicit range argument.
subagent-reports-complete-but-pr-unmerged
Catch the systematic gap between sub-agent "completed" status and the actual end state of a PR-merge orchestration task. Use when: (1) you've dispatched multiple parallel sub-agents (general-purpose or specialist) to open + review + merge PRs, (2) the parent receives with status: completed but the sub-agent's last…
git-monorepo-release
A release workflow for a monorepo—a single repository containing several packages that can each have their own version.
git-release-tag
A release helper for Git repositories that chooses a semantic version tag, such as patch, minor, or major, from the commits since the previous tag. It also builds release notes and can create a GitHub Release after confirmation.