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/xcodethink/open-claude-code-skillsWrote 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/xcodethink/open-claude-code-skills/ship)<a href="https://agentmods.dev/commands/xcodethink/open-claude-code-skills/ship"><img src="https://agentmods.dev/badge/commands/xcodethink/open-claude-code-skills/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/xcodethink/open-claude-code-skills/ship"><img src="https://agentmods.dev/badge/commands/xcodethink/open-claude-code-skills/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.00052 | $0.00442 |
| Opus 5.5 | $0.00021 | $0.00177 |
| Sonnet 5.5 | $0.00010 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
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 — 生产级开发闭环
用户输入 /ship $ARGUMENTS 触发生产级开发闭环：锁范围 → 开发 → 独立审计 → 测试+回归 → DoD 逐条验收 → 进度表 → 跨对话交接。
立刻读取并完整加载：
~/.claude/prompts/lib/09-元指令/生产级开发闭环.md
按其"行为契约"段严格执行，核心：
- 先锁范围 + 为每项写 DoD，等用户回"确认"再动手。
- 逐项闭环：开发 → 自验证 → 独立审计（挑刺视角）→ 测试+回归 → DoD 逐条验收；一个没验收不碰下一个。
- 每项收尾出进度表，通过才进下一项。
- 复用已有命令
/new-task（锁范围）、/dev（自主开发）、/done（完工汇报），不重复造轮子。 - 上下文快满 / 单项跨度大 → 停下，给可直接复制的下个对话引导词。
"本项目"靠当前窗口/文件夹确定；开局先报"项目/领域/套用标准"供用户纠正。
核心契约：DoD 逐条勾选 = 验收尺，"100% / 差不多"不是验收；审计不自夸；回归不漏；交接给可复制引导词。
参数: $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 · 25 lines · 52 tokens per session scan A 1d74c4e4cf8d
ship is a command published in the GitHub repository xcodethink/open-claude-code-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 442 once invoked, about $0.0002 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
implement-feature
Implement an approved feature plan with benefit-based placement, TDD, revision-bound evidence, and PR-ready output.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
zephyr-coverage-analysis
Analyze Zephyr test case coverage for a Jira user story and produce a QE management report with metrics, risk scoring, and prioritized recommendations.
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
test-suite
Run comprehensive test suite with coverage analysis.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.