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.
git clone --depth 1 https://github.com/dhslegen/digital-delivery-teamWrote 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/dhslegen/digital-delivery-team/ship)<a href="https://agentmods.dev/commands/dhslegen/digital-delivery-team/ship"><img src="https://agentmods.dev/badge/commands/dhslegen/digital-delivery-team/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/dhslegen/digital-delivery-team/ship"><img src="https://agentmods.dev/badge/commands/dhslegen/digital-delivery-team/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.00376 |
| Opus 5.5 | $0.00009 | $0.00150 |
| Sonnet 5.5 | $0.00005 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00038 |
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.
What it actually says
/ship
执行步骤
-
跑
/package- 若前置校验失败（测试覆盖率 < 70%、存在阻塞级评审项或
/impl校验失败未修复）→ 停止
- 若前置校验失败（测试覆盖率 < 70%、存在阻塞级评审项或
-
跑
/report- 若基线文件缺失 → 停止并按
/report指引在项目根目录封盘 - 若失败 → 停止
- 若基线文件缺失 → 停止并按
-
打包交付产物：
tar czf "delivery-${DDT_PROJECT_ID:-unknown}-$(date +%Y%m%d%H%M).tar.gz" \
README.md docs/ tests/test-report.md \
$(test -d web/dist && echo web/dist) \
$(test -d server/dist && echo server/dist) \
2>/dev/null || true
- 汇总输出：
/ship 完成
交付包: delivery-<id>-<ts>.tar.gz
总提效: <+n>%
质量守门: ✅ 通过 / ⚠️ <n> 项劣化
包含产物:
README.md
docs/
tests/test-report.md
web/dist/ （若存在）
server/dist/ （若存在）
若质量守门有劣化项：
❌ 存在质量劣化，禁止交付出包，请修复后重跑
/verify、/report与/ship
否则：
✅ 交付完成！
$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.
- 1mo ago First seen · 55 lines · 23 tokens per session scan A 139bd86f2122
ship is a command published in the GitHub repository dhslegen/digital-delivery-team (1 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 376 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-31.
Other commands, from other repositories
ship
Open a pull request for the current branch, drive it green, and merge it.
changelog-claude
Read the Claude Code changelog since the last run (plus the Claude Platform release notes for model changes), triage every entry against the global Claude Code setup, and apply the improvements the owner approves. Ledgered, so nothing is re-offered.
ship
Branch, commit, open PR, gather Claude + every enabled AI reviewer (Copilot, CodeRabbit, etc.), fix/justify/resolve every finding, loop until clean, then merge. Run only when implementation is finished AND the owner has said to ship (e.g. "ship it") — never self-invoke just because the work looks done. To design and…
release
Prepare a release of the sonu plugin — decide the semver bump, sync the version and plugin description across all five homes, run /validate, then hand to /sonu:ship. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.
ship
Complete PR workflow from commit to production with validation.
release
Cut a Major.Minor release from the Increment.