An automated command for preparing code to release. It updates the branch from the latest main branch, runs tests and review checks, creates a commit, pushes the changes, and opens a pull request for team review.

Use it when a feature branch is ready to merge and publish as a pull request.

It removes the need to perform the usual release steps manually and stops when conflicts, failed tests, or critical review problems need attention.

ship — Command by drag88

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.

agentmods

npx agentmods add commands/drag88/claude-dev-framework/ship

Clone the repo

git clone --depth 1 https://github.com/drag88/claude-dev-framework

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00022	$0.01050
Opus 5	$0.00011	$0.00525
Sonnet 5	$0.00004	$0.00210
Haiku 4.5	$0.00002	$0.00105

Measured yesterday against content hash 7a50e513b56c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

commands/ship.md · 104 lines

How it starts

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

/cdf:ship — Automated Release Pipeline

You are running the /cdf:ship workflow. This is non-interactive and fully automated. Do NOT ask for confirmation at any step. The user said /cdf:ship which means DO IT.

Only stop for:

On main branch (abort)
Merge conflicts that can't be auto-resolved
Test failures
CRITICAL review findings (one question per issue with fix recommendation)

Never stop for:

Uncommitted changes (always include them)
Commit message approval
PR body content

Step 1: Pre-flight

Check current branch. If on main, abort: "You're on main. Ship from a feature branch."
Run git status (never use -uall). Uncommitted changes are always included.
Run git diff main...HEAD --stat and git log main..HEAD --oneline to understand what's being shipped.
Print a brief summary of what will be shipped.

Step 2: Merge origin/main

Merge latest main so tests run against the merged state:

git fetch origin main && git merge origin/main --no-edit

If merge conflicts: try auto-resolve for simple cases (lock files, generated files). If complex or ambiguous, STOP and show conflicts.

If already up to date: continue silently.

Step 3: Run Tests

Detect and run the project's test suite. Check for these in order:

package.json → look for test, test:unit, test:integration scripts
pytest.ini, pyproject.toml, setup.cfg → run pytest
Gemfile → run bundle exec rspec or bin/rails test
Makefile → look for test target
go.mod → run go test ./...

Run all discovered test suites. If multiple exist (e.g., backend + frontend), run them in parallel.

If any test fails: Show failures and STOP. Do not proceed. If all pass: Note counts briefly and continue.

Step 4: Pre-Landing Review

Delegate pre-landing diff review to the compound-engineering:ce-code-review host skill.

Requires: the compound-engineering plugin. If it is not installed, stop and tell the user to install the compound-engineering plugin for their host (install commands are in the README) — do not improvise a replacement flow.

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

yesterday First seen · 104 lines · 22 tokens per session scan A 7a50e513b56c

Subscribe to this mod's changes

ship is a command published in the GitHub repository drag88/claude-dev-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,050 once invoked, about $0.0001 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.

Code review Git and workflow Testing

ship

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/cdf:ship — Automated Release Pipeline

Step 1: Pre-flight

Step 2: Merge origin/main

Step 3: Run Tests

Step 4: Pre-Landing Review

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement