A release-readiness checklist for finished code, documentation, configuration, or other project work.

Use it after development or documentation work when you need a GO/NO-GO decision before shipping.

It gathers the evidence needed to decide whether work is ready to publish, merge, deploy, or close. It also catches conflicts with the project's stated goals and safety requirements.

ship — Skill for Claude Code by 0xmariowu

Install

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.

Any agent

npx skills add 0xmariowu/builders-dont-cry --skill ship

Clone the repo

git clone --depth 1 https://github.com/0xmariowu/builders-dont-cry

Made for: Claude Code.

Or install builders-dont-cry, the plugin that ships this one along with the rest of its 12 skills, 10 commands, 3 agents, 5 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/0xmariowu/builders-dont-cry/ship/github.svg)](https://agentmods.dev/skills/0xmariowu/builders-dont-cry/ship)

Your own site

<a href="https://agentmods.dev/skills/0xmariowu/builders-dont-cry/ship"><img src="https://agentmods.dev/badge/skills/0xmariowu/builders-dont-cry/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/0xmariowu/builders-dont-cry/ship"><img src="https://agentmods.dev/badge/skills/0xmariowu/builders-dont-cry/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,250 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00037	$0.01250
Opus 5	$0.00018	$0.00625
Sonnet 5	$0.00007	$0.00250
Haiku 4.5	$0.00004	$0.00125

Measured 10d ago against content hash 99d773949de0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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 10d 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.

core/skills/ship/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/ship — Local-First Release Gate

Step 0: Escape Hatch

If the user says 别走流程, 直接做, 简单点, or 不走地图, do not force /ship. Acknowledge once and do the smallest direct action.

Exception: do not bypass safety gates for deploy, public upload, database migration, force push, destructive writes, or secret exposure.

Step 0.5: Project Goal Check

If PROJECT_GOAL.md exists in the project root, read it before GO/NO-GO. If the package conflicts with current_phase, exit_criteria, or out_of_scope, return NO-GO unless the owner explicitly accepts the conflict.

Contract

Decide whether the current work is ready to ship. /ship is local-first: it does not assume GitHub, PRs, remote pushes, or public release unless the project workflow requires them.

Process

Determine project type and workflow:
- local BDC / docs / config
- app or package
- GitHub PR / publish / deploy workflow
Gather evidence:
- current git status and diff stat
- plan status if plan-driven
- latest /verify verdict if present
- whether latest /verify verdict includes Verified HEAD: <short-sha> matching current HEAD
- latest test/lint/health evidence
For BDC changes:
- default: run or require /health --quick
- broader local confidence: run or require /health --baseline
- do not bypass /health by directly invoking health internals
Apply size and intent gate.
Return GO / NO-GO with rollback or restore plan.

Verify Freshness Gate

/ship consumes /verify; it does not re-run code/test/security fan-out by default.

For non-trivial code, BDC behavior, release, merge, publish, or deploy work:

Get current HEAD with git rev-parse --short HEAD when inside a git repository.
Find the latest /verify verdict in the current context or a project-local verify marker if one exists.
Require that verdict to include Verified HEAD: <short-sha> matching current HEAD.
If no matching verdict exists, return NO-GO and make the next action run /verify or /verify --deep.
If the latest matching verdict is REQUEST_CHANGES, return NO-GO and point to its blockers.

Read the full file on GitHub · 108 lines

Changes

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.

10d ago First seen · 108 lines · 37 tokens per session scan A 99d773949de0

Subscribe to this mod's changes

ship is a skill published in the GitHub repository 0xmariowu/builders-dont-cry (4 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 1,250 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-08-31.

Git and workflow Releases

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

multi-agent-release-manager

Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.

chromium/chromium · 27 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

pack-submit

Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.

aeonfun/aeon · 27 tokens

updater_guide

Guidance for checking for and installing Row-Bot updates.

siddsachar/row-bot · 17 tokens

nvca-chart-release

Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.

NVIDIA/nvcf · 61 tokens