A production-release checklist and deployment command. It runs tests, checks for debug leftovers and risky files, reviews web performance, verifies the build, and then deploys.

Use it before every production deployment to check the project and start its deployment process.

It catches common problems before code reaches production, including failing tests, debugging code, local URLs, and build errors.

ship — Command for Claude Code by mizukaizen

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.

Clone the repo

git clone --depth 1 https://github.com/mizukaizen/hive-doctrine-mcp

Made for: Claude Code.

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/commands/mizukaizen/hive-doctrine-mcp/ship/github.svg)](https://agentmods.dev/commands/mizukaizen/hive-doctrine-mcp/ship)

Your own site

<a href="https://agentmods.dev/commands/mizukaizen/hive-doctrine-mcp/ship"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/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/commands/mizukaizen/hive-doctrine-mcp/ship"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 408 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.00000	$0.00408
Opus 5	$0.00000	$0.00204
Sonnet 5	$0.00000	$0.00082
Haiku 4.5	$0.00000	$0.00041

Measured 11d ago against content hash 9870eeed386b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 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.

gated-products/honey/claude-packages/HD-4001-solo-founder/commands/ship.md · 59 lines

What it actually says

Command: /ship

Pre-ship checklist and deployment. Run this before every production deploy.

Usage

/ship

Process

Step 1: Run Tests

Execute the project's test suite. If any test fails, stop and report the failure. Do not proceed until tests pass.

# Detect and run the appropriate test command
# npm test / pytest / cargo test / etc.

Step 2: Check for Debug Artifacts

Scan the codebase for common debug artifacts that should not ship:

console.log / console.error / console.warn statements (unless in a logging utility)
debugger statements
TODO or FIXME comments added in the current diff
Hardcoded localhost URLs
.env files staged for commit

Report any findings. The founder decides whether to fix or ship anyway.

Step 3: Performance Check

If the project has a web frontend, run a Lighthouse audit (or equivalent):

Performance score must be above 80
Accessibility score must be above 90
Flag any image over 500KB that is not optimised

Step 4: Build Verification

Run the production build. It must complete without errors or warnings.

# npm run build / cargo build --release / etc.

Step 5: Deploy

Execute the project's deploy command. Verify the deployment is live by checking the production URL or running a smoke test.

Step 6: Post-Deploy

Update CHANGELOG.md with what shipped and today's date
Confirm the core user flow works on production
Report: "Shipped. [summary of what went live]"

Rules

If any step fails, stop and report. Do not skip steps.
The founder can override any warning with explicit confirmation.
Total deploy time target: under 5 minutes from /ship to live.

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.

11d ago First seen · 59 lines · 0 tokens per session scan A 9870eeed386b

Subscribe to this mod's changes

ship is a command published in the GitHub repository mizukaizen/hive-doctrine-mcp (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 408 tokens. 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.

AI Safety DevOps and cloud Git and workflow Multi-Agent Releases agent-marketplace ai-agents mcp mcp-server

ship