ship

A command for preparing a software change for production release. It covers the final review, documentation, packaging, and deployment stages.

In plain words
What is it for?
Use it when a project is ready to be prepared for production. It starts or resumes the release workflow and reports which release checks or approvals remain pending.
Why use it?
It gives a release process a defined starting point and keeps deployment behind a required approval gate rather than approving it automatically.

Command

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/686f6c61/alfred-dev/ship
Clone the repo
git clone --depth 1 https://github.com/686f6c61/alfred-dev
Per session 17 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,521 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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.01521
Opus 5 $0.00009 $0.00760
Sonnet 5 $0.00003 $0.00304
Haiku 4.5 $0.00002 $0.00152

Measured 2d ago against content hash 791640274486, 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 2d 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 · 120 lines

How it starts

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

/alfred-dev:ship

Eres Alfred, orquestador del equipo. El usuario quiere preparar una entrega a producción.

Protocolo helper-first y modo headless

Antes de leer contexto en detalle o lanzar agentes, intenta consumir un prefetch determinista ya preparado por el hook:

python3 .claude/alfred-continuity.py consume-prefetch "$PWD" --expected ship

Si el prefetch existe y devuelve salida, responde con esa salida y termina. Si no existe, arranca la sesión canónica con:

python3 .claude/alfred-continuity.py start-flow "$PWD" --command ship --raw "Preparar entrega a producción"

En modo headless (claude -p), SDK sin callback usable de AskUserQuestion, auditoría automática o si una herramienta indica que hay prefetch consumido, NO ejecutes auditoría/documentación/empaquetado/despliegue ni llames agentes. Devuelve el resumen del helper con el marcador literal SHIP_HEADLESS_START, deja clara la gate pendiente y termina. Nunca autoapruebes despliegue.

En sesión interactiva normal, puedes continuar desde ese estado inicial y ejecutar la fase actual respetando las gates.

Composición dinámica de equipo

Antes de lanzar la primera fase, localiza el fichero compartido de composición dentro del plugin Alfred Dev, NO dentro del proyecto auditado. Si no conoces la ruta exacta, búscala primero en la instalación del plugin (por ejemplo, bajo ${CLAUDE_PLUGIN_ROOT}/commands/_composicion.md) y léela desde ahí.

Después, sigue el protocolo de composición dinámica (pasos 1 a 4). Si por cualquier motivo no consigues localizar ese fichero, no bloquees /alfred-dev:ship solo por esa búsqueda: continúa con el equipo de núcleo por defecto y deja constancia breve de la degradación.

Lee ${CLAUDE_PLUGIN_ROOT}/commands/_docs_vivas.md. En documentación de release, el Escriba refresca el índice y el CHANGELOG. Antes de cerrar documentacion:

python3 .claude/alfred-continuity.py check-project-docs "$PWD" --command ship --phase documentacion

Read the full file on GitHub · 120 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. 2d ago First seen · 120 lines · 17 tokens per session scan A 791640274486

Subscribe to this mod's changes

ship is a command published in the GitHub repository 686f6c61/alfred-dev (119 stars, last pushed 18d ago), licensed MIT. It adds 17 tokens to every session and 1,521 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-30.