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/trygit 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/try)<a href="https://agentmods.dev/commands/bonnguyenitc/specship/try"><img src="https://agentmods.dev/badge/commands/bonnguyenitc/specship/try.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.00014 | $0.00256 |
| Opus 5 | $0.00007 | $0.00128 |
| Sonnet 5 | $0.00003 | $0.00051 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
try 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 3d 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
Verify the CLI end-to-end with a real install (flags: $ARGUMENTS, default --all).
- Create a scratch dir and install:
d=$(mktemp -d) && node bin/cli.js init ${ARGUMENTS:---all} --dir "$d" && echo "$d" - Inspect the tree (
find "$d" -type f) and check:- skills landed at each agent's native path (
.claude/skills,.codex/skills,.cursor/skills,.agent/skills) - the doc merged/wrote correctly (marker block
<!-- specship:start -->appears exactly once in CLAUDE.md / AGENTS.md) openai.yamlmanifests exist under.codex/skills/*/agents/only
- skills landed at each agent's native path (
- Re-run the same init command and confirm it is idempotent (still one marker block, user-modified files kept).
- Report what you verified and anything that looks wrong.
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.
- 3d ago First seen · 19 lines · 14 tokens per session scan A 564c990050e7
try is a command published in the GitHub repository bonnguyenitc/specship (2 stars, last pushed 25d ago), licensed MIT. It adds 14 tokens to every session and 256 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
roo-resolve-conflicts
Resolve merge conflicts intelligently using git history analysis.
status
Run Tau Git Memory status now.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.