Borrowing it
Nothing to install: this file belongs to davidbuenov/dbv-specs-ops. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/davidbuenov/dbv-specs-ops/master/.claude/commands/ship.mdgit clone --depth 1 https://github.com/davidbuenov/dbv-specs-opsWrote 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.
[](https://agentmods.dev/commands/davidbuenov/dbv-specs-ops/ship)<a href="https://agentmods.dev/commands/davidbuenov/dbv-specs-ops/ship"><img src="https://agentmods.dev/badge/commands/davidbuenov/dbv-specs-ops/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.
<a href="https://agentmods.dev/commands/davidbuenov/dbv-specs-ops/ship"><img src="https://agentmods.dev/badge/commands/davidbuenov/dbv-specs-ops/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00023 | $0.00846 |
| Opus 5.5 | $0.00009 | $0.00338 |
| Sonnet 5.5 | $0.00005 | $0.00169 |
| Haiku 4.5 | $0.00002 | $0.00085 |
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 4d 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.
This is a copy
100% identical to ship — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Ejecuta ahora la fase Ship (/ship) del ciclo Spec→Plan→Build→Test→Simplify→Ship definido en
dbv-specs-ops/docs/MASTER_PROMPT.md (<workflow>, paso 6). No cierres esta fase si quedan hallazgos
Crítico sin resolver de la revisión de /code-simplify (dbv-specs-ops/docs/REVIEW.md). Actualiza el
README.md de la raíz, completa dbv-specs-ops/walkthrough.md, pregunta el tipo de versión (Patch/Minor/
Major), publica dbv-specs-ops/CHANGELOG.md y propone el commit + tag de git (sin hacer push). Si el
remoto es GitHub, ofrece una vez el Release automático o manual (dbv-specs-ops/scripts/release-notes.py).
🕸️ Grafo de fases — nodo activo: Ship
Fase 6: Memory Gate, documentación, versión semántica, CHANGELOG y tag de git.
Al entrar — la transición por la que llegas fija la condición, cómo ejecutar esta fase y qué evitar:
- desde Simplify (CONVERGES_TO) — si: Cero hallazgos Crítico, dbv-lint.py sin errores (si aplica) y tests en verde tras el refactor.
- Cómo: Imprime <memory_update_proposal>. Actualiza README.md de la raíz, sincroniza DESIGN.md derivado si existe, completa walkthrough.md, pregunta el tipo de versión, publica CHANGELOG.md y propone commit + tag.
- Evita: No ejecutes git push (solo sugiérelo). No cierres sin <memory_update_proposal>. No generes start/stop en apps de escritorio, librerías o CLIs.
Salidas (salto 1) — a dónde puedes ir y con qué condición:
- Ship → Simplify (TRIGGERS) — si: El gate de /ship encuentra un hallazgo Crítico sin resolver o la documentación contradice el código.
- Cómo: Vuelve a la revisión por pases solo para resolver lo que bloquea la entrega.
- Evita: No publiques una versión con un Crítico abierto.
- Ship → End (LEADS_TO) — si: Versión elegida por el usuario, CHANGELOG.md publicado, commit y tag propuestos.
- Cómo: Guarda el Snapshot de Contexto en task.md y resume al usuario lo entregado.
- Evita: No dejes ficheros temporales ni cambios sin reflejar en task.md.
Horizonte (salto 2) — lo que vendrá después y revisará tu trabajo:
- Simplify → Build (TRIGGERS) — si: La revisión deja un hallazgo Crítico que exige cambiar el comportamiento del código, o un refactor rompe los tests.
- Cómo: Vuelve a Build solo para ese hallazgo y repasa Test antes de regresar a Simplify.
- Evita: No mezcles la corrección con funcionalidad nueva. No ocultes el hallazgo rebajando su severidad.
- Simplify ↩ Ship (CONVERGES_TO) — si: Cero hallazgos Crítico, dbv-lint.py sin errores (si aplica) y tests en verde tras el refactor.
Rutas relativas a dbv-specs-ops/. Lee la 🚫 Rejection Memory de memory.md antes de proponer un enfoque: lo que ya se descartó no se vuelve a proponer sin explicar qué ha cambiado.
$ARGUMENTS
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.
- 4d ago Changed · +28 lines fe0947738ae8
- 1mo ago First seen · 11 lines · 23 tokens per session scan A 2e65d16f102e
ship is a command published in the GitHub repository davidbuenov/dbv-specs-ops (29 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 846 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to ship, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
doc-changelog
Generation and maintenance of the project changelog.