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/bonnguyenitc/specship/releasegit clone --depth 1 https://github.com/bonnguyenitc/specshipWrote 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/bonnguyenitc/specship/release)<a href="https://agentmods.dev/commands/bonnguyenitc/specship/release"><img src="https://agentmods.dev/badge/commands/bonnguyenitc/specship/release.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.00228 |
| Opus 5 | $0.00006 | $0.00114 |
| Sonnet 5 | $0.00003 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
release 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.
What it actually says
Release specship ($ARGUMENTS, e.g. patch).
- Preconditions: working tree clean (
git status), onmain,npm testpasses. - Dry run first:
./publish.sh $ARGUMENTS --dry-runand review the packed file list — it must containbin/,src/,skills/, the per-agent doc templates (.claude/CLAUDE.md,.codex/AGENTS.md,.cursor/WORKFLOW.mdc,.antigravity/rules.md) and README, and must NOT contain.claude/settings.json,.claude/commands/,tasks/, or test scratch files. - Show me the dry-run output and stop for confirmation — the real publish
(
./publish.sh $ARGUMENTS) prompts for confirmation and may need an npm OTP, so I run that step.
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 First seen · 18 lines · 13 tokens per session scan A d7025faf4cf4
release is a command published in the GitHub repository bonnguyenitc/specship (2 stars, last pushed 26d ago), licensed MIT. It adds 13 tokens to every session and 228 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-31.
Other commands, from other repositories
cli-release
Prepare a new release of the CoStrict CLI.
release
Create a new release of the CoStrict extension.
CHANGELOG
Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.
release
Command "release" from Besty0728/Unity-Skills, covering release workflow — 候选矩阵 → main/tag → 正式 release, 输入, 阶段 1：只读预检查, 阶段 2：生成并审阅 release note and v{version} — {一句话总结，提炼 2-4 个核心特性}.
chunkhound-release-notes
Generate release notes for a ChunkHound production release.
create-manifest
Create a migration manifest for a new patch, beta, rc, or minor release based on commits since the previous release.