A deployment command that validates a feature, sends it through staging when available, and deploys it to production after approval. Staging is a separate environment used to test a change before users see it.

Use it to deploy changes through staging to production, or to deploy directly when the project has no staging workflow, while recording deployment details.

It organizes pre-deployment checks, approval, release creation, and deployment records while supporting rollback testing and different deployment setups.

ship — Command for Claude Code by marcusgoll/Spec-Flow

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/marcusgoll/Spec-Flow

agentmods

npx agentmods add commands/marcusgoll/spec-flow/ship

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/marcusgoll/spec-flow/ship/github.svg)](https://agentmods.dev/commands/marcusgoll/spec-flow/ship)

Your own site

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

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

When invoked 9,631 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.00013	$0.09631
Opus 5.5	$0.00005	$0.03852
Sonnet 5.5	$0.00003	$0.01926
Haiku 4.5	$0.00001	$0.00963

Measured 1mo ago against content hash 71c17fe222a5, 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 1mo 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.

.claude/commands/deployment/ship.md · 1,218 lines

How it starts

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

/ship — Unified Deployment Orchestrator (Thin Wrapper)

v11.0 Architecture: This command spawns the isolated ship-phase-agent via Task(). Deployment operations run in isolated context with question batching for production approval.

Active Feature: !ls -td specs/[0-9]*-* 2>/dev/null | head -1 || echo "none"

Interaction State: !cat specs/*/interaction-state.yaml 2>/dev/null | head -10 || echo "none"

Deployment Model: !test -f .github/workflows/deploy-staging.yml && echo "staging-prod" || (git remote 2>/dev/null && echo "direct-prod" || echo "local-only")

Architecture (v11.0 - Phase Isolation):

/ship → Task(ship-phase-agent) → Q&A for prod approval → deployment

Agent responsibilities:

Auto-detect deployment model (staging-prod, direct-prod, local-only)
Execute pre-flight validation
Deploy to staging (auto-proceed)
Request approval for production deployment (returns question)
Create GitHub release
Record deployment metadata

Deployment Models (auto-detected):

staging-prod: Automated staging validation before production (recommended)
- Detection: Git remote + staging branch + .github/workflows/deploy-staging.yml
- Workflow: pre-flight + optimize (parallel) → deploy-staging → automated validation → deploy-prod → finalize
direct-prod: Direct production deployment without staging
- Detection: Git remote + no staging branch
- Workflow: pre-flight + optimize (parallel) → deploy-prod → finalize
local-only: Local build and integration only
- Detection: No git remote
- Workflow: pre-flight + optimize (parallel) → build-local → merge to main → finalize

Automation Features:

Pre-flight + optimize run in parallel (saves ~10 minutes)
Zero manual gates (removed /preview, interactive version selection)
Auto-generated validation reports (E2E, Lighthouse, rollback tests)
Platform API-based deployment ID extraction (no log parsing)
Auto-fix CI failures via GitHub Actions

Arguments:

(empty): Start deployment workflow from beginning
continue: Resume from last completed phase (if failure occurred)
status: Display current deployment status and exit
rollback [version]: Rollback to previous deployment version (v10.14+)
recover: Recover corrupted state.yaml from git history (v10.14+)
budget: Display deployment quota status
--auto: Full autopilot mode - skip prompts, auto-merge when CI passes, continue to finalize (v11.7)

Dependencies: Requires completed /implement phase

Timing: 25-35 minutes fully automated

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

1mo ago First seen · 1,218 lines · 13 tokens per session scan A 71c17fe222a5

Subscribe to this mod's changes

ship is a command published in the GitHub repository marcusgoll/Spec-Flow (96 stars, last pushed 24d ago), licensed MIT. It adds 13 tokens to every session and 9,631 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.

CI and CD DevOps and cloud Git and workflow Releases ai-agents ai-assisted-development ai-workflows automation bash claude

ci

Run CI validation, create PRs, and merge on green.

Generous-Corp/pulp · 14 tokens

land-and-deploy

Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.

FlorianBruniaux/claude-code-plugins · 23 tokens

devops

You are the DevOps Specialist -- the single authority on version control, CI/CD pipelines, platform operations (GitHub, Azure DevOps, GitLab), infrastructure, deployment, backup, and cleanup. If it touches git, pipelines, or production infrastructure, it's yours.

samibs/skillfoundry · 0 tokens

ship