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.
npx agentmods add commands/luanmorenommaciel/agentspec/shipgit clone --depth 1 https://github.com/luanmorenommaciel/agentspecWrote 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/luanmorenommaciel/agentspec/ship)<a href="https://agentmods.dev/commands/luanmorenommaciel/agentspec/ship"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/agentspec/ship.svg" alt="Measured on agentmods" 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 | $0.00013 | $0.00471 |
| Opus 5 | $0.00006 | $0.00235 |
| Sonnet 5 | $0.00003 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
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.
What it actually says
Ship Command
Archive completed feature with lessons learned (Phase 4)
Usage
/ship <define-file>
Examples
/ship .claude/sdd/features/DEFINE_NOTIFICATION_SYSTEM.md
/ship DEFINE_USER_AUTH.md
Overview
This is Phase 4 — the close of the 5-phase AgentSpec workflow:
Phase 0: /brainstorm → .claude/sdd/features/BRAINSTORM_{FEATURE}.md (optional)
Phase 1: /define → .claude/sdd/features/DEFINE_{FEATURE}.md
Phase 2: /design → .claude/sdd/features/DESIGN_{FEATURE}.md
Phase 3: /build → Code + .claude/sdd/reports/BUILD_REPORT_{FEATURE}.md
Phase 4: /ship → .claude/sdd/archive/{FEATURE}/SHIPPED_{DATE}.md (THIS COMMAND)
What Happens
- Load the skill — read
.claude/skills/sdd-ship/SKILL.md; it owns the full ship methodology. - Verify completeness — all artifacts present, BUILD_REPORT complete, all tests passing. An incomplete build is refused and routed back to
/build. - Archive — copy every phase artifact to
.claude/sdd/archive/{FEATURE}/and update all document statuses to "Shipped". - Extract lessons — capture specific, actionable lessons learned in the SHIPPED document (per
SHIPPED_TEMPLATE.md). - Close the cycle — clean the working files from
features/andreports/, then hand off. Start the next feature with/define.
References
- Skill:
.claude/skills/sdd-ship/SKILL.md - Agent:
.claude/agents/workflow/ship-agent.md - Template:
.claude/sdd/templates/SHIPPED_TEMPLATE.md - Contracts:
.claude/sdd/architecture/WORKFLOW_CONTRACTS.yaml - Previous Phase:
.claude/commands/workflow/build.md
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.
- 2d ago First seen · 56 lines · 13 tokens per session scan A a0283218878b
ship is a command published in the GitHub repository luanmorenommaciel/agentspec (244 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 471 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-09-01.
Other commands, from other repositories
changelog
Generate a new changelog entry by reading all changeset files and creating a properly formatted entry in .changelog/v3.mdx.
review-renovate
Review and merge renovate PRs with automerge configuration updates.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
merge-and-status
Merge the current PR, pull main, surface any open contributor PRs and untriaged contributor issues, and show open milestone issues.
release
Prepare a release by updating docs and bumping the version.
ship
Deliver the increment. Then go live with a rollback you have run.