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/yudefine/nuxt-supabase-starter/shipgit clone --depth 1 https://github.com/YuDefine/nuxt-supabase-starterWrote 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/yudefine/nuxt-supabase-starter/ship)<a href="https://agentmods.dev/commands/yudefine/nuxt-supabase-starter/ship"><img src="https://agentmods.dev/badge/commands/yudefine/nuxt-supabase-starter/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.1 | $0.00010 | $0.00333 |
| Opus 5 | $0.00005 | $0.00167 |
| Sonnet 5 | $0.00002 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00033 |
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 6d 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 — 自動發布
Pre-flight 檢查
- 確認不在
mainbranch（git branch --show-current） - 確認有未 push 的 commits（
git log origin/HEAD..HEAD --oneline） - 確認沒有未提交的變更（
git status --porcelain）
如果任何檢查失敗，告知使用者並停止。
Step 1: 品質檢查
pnpm check
如果失敗：
- 嘗試自動修復（format/lint auto-fix）
- 重新執行
pnpm check - 如果仍然失敗 → 報告錯誤並停止
Step 2: Push
git push -u origin HEAD
Step 3: 建立 PR
使用 gh pr create：
- Title: 從 commits 摘要生成（簡潔、< 70 字元）
- Body: 包含 Summary、Test Plan、Co-Authored-By
格式：
gh pr create --title "PR title" --body "$(cat <<'EOF'
## Summary
- bullet points
## Test plan
- [ ] checklist
🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
Step 4: 報告
輸出 PR URL 和摘要。
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.
- 6d ago First seen · 58 lines · 10 tokens per session scan A 203cce2cff10
ship is a command published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 333 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-30.
Other commands, from other repositories
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.
web-build-fix
Diagnose and resolve web build, bundling, or deployment issues.
speckit.tdd.plan
Derive the feature's test list by delegating to zfa tdd plan (deterministic engine); falls back to LLM-guided derivation only when zfa is unavailable.
p5-impl-green
Writes the minimal production code that makes the existing tests green. No over-engineering.
tdd
Test-driven development with TodoWrite planning and comprehensive testing.
tdd
Test-driven development with TodoWrite planning and comprehensive testing.