agentmods.dev

ship

ship is a command for Claude Code from dwarvesf/dwarves-kit. It costs 28 tokens per session (4,838 once invoked), scanned A, original, MIT.

A release command that guides a finished software change through review, testing, version updates, changelog work, documentation, a conventional commit, and a pull request. A pull request is a proposal to merge changes into a shared codebase.

In plain words
What is it for?
Verifying the active specification's review decision, reporting missing build decisions or companion-document updates, running the release steps, and preparing the change for merging.
Why use it?
It checks important release requirements before work is merged and stops when the recorded review says the change should not ship.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions CLAUDE.md.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is bash lib/goal/goal-drafts.sh archive.

Part of the kit plugin — 14 skills, 39 commands, 31 agents, 10 hooks shipped together

not rated 11repo +1 changed 8d ago A scan 28 tokens original MIT

Good fit Verifying the active specification's review decision, reporting missing build decisions or companion-document updates, running the release steps, and preparing the change for merging.

Compare 6 commands from other repositories ↓
View source ↗ dwarvesf/dwarves-kit
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/dwarvesf/dwarves-kit
agentmods
npx agentmods add commands/dwarvesf/dwarves-kit/ship

Made for: Claude Code.

Or install kit, the plugin that ships this one along with the rest of its 14 skills, 39 commands, 31 agents, 10 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.

agentmods badge for ship

README.md
[![agentmods](https://agentmods.dev/badge/commands/dwarvesf/dwarves-kit/ship/github.svg)](https://agentmods.dev/commands/dwarvesf/dwarves-kit/ship)
Your own site
<a href="https://agentmods.dev/commands/dwarvesf/dwarves-kit/ship"><img src="https://agentmods.dev/badge/commands/dwarvesf/dwarves-kit/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.

agentmods 80×15 button for ship

Your own site · 80×15
<a href="https://agentmods.dev/commands/dwarvesf/dwarves-kit/ship"><img src="https://agentmods.dev/badge/commands/dwarvesf/dwarves-kit/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,838 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.04838
Opus 5.5 $0.00011 $0.01935
Sonnet 5.5 $0.00006 $0.00968
Haiku 4.5 $0.00003 $0.00484

Measured 8d ago against content hash 36b5a1ba87bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 8d 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.

commands/ship.md · 237 lines

How it starts

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

You are a release engineer. The user says the feature is done. Your job is to verify, package, and ship it cleanly.

Process

Step 1: Review gate

Check if a review has been done:

  • Resolve the active spec (docs/specs/SPEC-NNN-<slug>.md, the active-spec convention) and read its ## Review section verdict.
  • If verdict is SHIP or FIX THEN SHIP (with fixes applied): proceed.
  • If verdict is DO NOT SHIP: STOP. Tell the user to fix the issues first.
  • If the spec has no ## Review section: WARN. Ask: "(A) Run /kit:review first / (B) Run /kit:review-team for thorough review / (C) Skip review and ship anyway"

Do not silently skip the review check. The user must explicitly choose to ship without review.

Step 1b: Completeness log (warn, not block)

Read ~/.claude/dwarves-kit/logs/completeness.log (the warn+log sink from the WORKFLOW completeness clauses). Surface any entries since the last ship/tag: lost build-decisions (decision-translation) and un-updated companion docs (doc-update, per the WORKFLOW doc-impact map). REPORT them so the maintainer decides; do NOT auto-block on completeness. Hard blocks stay reserved for the spec's ## Review DO-NOT-SHIP verdict and the safety gates. If the log is absent or empty, say "completeness: clean".

Step 1c: End-user guide check (warn, not block)

Apply the test: does this change have an end user who is not the builder? A library, an internal tool, or infra with no such user is exempt.

If yes: confirm GUIDE.md exists at the product root and still matches what shipped (what it does, how to use it, what to do when it breaks). Template: docs/GUIDE.template.md.

If GUIDE.md is missing or stale, REPORT it to the maintainer; do NOT block the ship. Same voice as Step 1b / Step 4a: hard blocks stay reserved for the spec's ## Review DO-NOT-SHIP verdict and the safety gates.

Step 2: Run tests

Detect the test runner and execute:

  • Node.js: npm test or pnpm test or yarn test
  • Go: go test ./...
  • Python: pytest or python -m pytest
  • Rust: cargo test

Read the full file on GitHub · 237 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.

  1. 8d ago Changed · +12 lines 36b5a1ba87bc
  2. 13d ago Changed eb2b9a24afba
  3. 15d ago Changed · +1 lines e2be09100002
  4. 21d ago Changed · +5 lines d90637cf37d2
  5. 1mo ago Changed c677af039616
  6. 1mo ago Changed 75673db17766
  7. 1mo ago Changed · +1 lines 855dc5011f0d
  8. 1mo ago Changed · +2 lines 716d2af1ee02
  9. 1mo ago First seen · 216 lines · 28 tokens per session scan A df46fe4c1477

Subscribe to this mod's changes

ship is a command published in the GitHub repository dwarvesf/dwarves-kit (11 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 4,838 once invoked, about $0.0001 per session on Opus 5.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-30.

Claude CodeGit and workflowReleasesclaude-code-hooksdeveloper-toolsspec-driven-developmentworkflow
Related

Other commands, from other repositories

land

Resolve and squash merge one named, currently authorized pull request.

gmickel/flow-next · 13 tokens

release

Verify, write the CHANGELOG, cut a version — then hand the release sequence back.

hamr0/agentic-toolkit · 17 tokens

ship

Run /ship — see .claude/commands/ship.md for the authoritative spec.

loiane/specs-driven-development-spring-angular · 18 tokens

mode

Show or switch the project's conformance mode between Enforced and À la carte, within the set the organization allows.

akka/ai-marketplace · 23 tokens

ship

Run the auditors for every exit condition in scope for the requested ship target (review or release), and on pass run the ship steps the organization declared for that target.

akka/ai-marketplace · 33 tokens

pr-package

Prepare a GitHub PR delivery package (branch, commits, PR title and body, reviewer notes) from the real git diff against an explicit base branch, persisted as PRPACKAGE.md, never inventing work outside the diff. Use when scope is done and diff is stable. Do not use mid-implementation, for a branch name (use…

Mozurok/fhorja.dev · 109 tokens