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 skills add bonnguyenitc/specship --skill ss-shipgit 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/skills/bonnguyenitc/specship/ss-ship)<a href="https://agentmods.dev/skills/bonnguyenitc/specship/ss-ship"><img src="https://agentmods.dev/badge/skills/bonnguyenitc/specship/ss-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/skills/bonnguyenitc/specship/ss-ship"><img src="https://agentmods.dev/badge/skills/bonnguyenitc/specship/ss-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.00092 | $0.01913 |
| Opus 5 | $0.00046 | $0.00957 |
| Sonnet 5 | $0.00018 | $0.00383 |
| Haiku 4.5 | $0.00009 | $0.00191 |
Grade A, and why
ss-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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship
Goal: given a feature request (e.g. /ss-ship thực hiện chức năng login), drive the task through the whole pipeline in a single run — spec → plan → coding → review, attaching debug whenever a defect appears — stopping only when genuinely blocked.
ss-ship is an orchestrator, not a stage: it doesn't replace the stage skills, it invokes them in order and carries the user's consent across the handoffs where each stage would normally stop and ask. Invoking ss-ship is that consent, granted once for the whole task.
When to use
- The user hands you a feature request, ticket, or PRD — anything the
ss-specskill could consume — and wants it taken all the way to reviewed code. - Also works mid-pipeline: if the task already has artifacts (a confirmed
spec.md, an approvedplan.md), start from the first incomplete stage instead of redoing finished ones. - Not for codebase exploration: this skill never runs
ss-explore-source. Ifdocs/onboarding/*is missing and the codebase is unfamiliar, tell the user to run it first rather than shipping blind.
Shared task state
Part of the task pipeline — see ../WORKFLOW.md for the full contract. Every rule there (artifacts, IDs, preconditions, traces, lessons) applies unchanged; the only thing ss-ship overrides is the per-handoff "ask the user" step.
- Hydrate: if the request matches an existing task (explicit
TASK-<ID>, or one in conversation), resume it from its current stage; otherwise thespecstage will open a new task. If that named task is shelved (status: paused, or found undertasks/archive/), un-shelve it first exactly asss-resume-taskdoes (restore the folder and/or flippaused→active, with the dated log trace) before advancing. Readtasks/LESSONS.mdif present. - Checkpoint: each stage skill does its own checkpointing. Additionally, log every auto-advance as a dated Pipeline Log line in
task.md, e.g.- <YYYY-MM-DD HH:MM +TZ> ship: auto-advanced spec → plan— carrying your agent label (format:../WORKFLOW.md→ Agent handoff).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 50 lines · 92 tokens per session scan A 36afa0d36d63
ss-ship is a skill published in the GitHub repository bonnguyenitc/specship (2 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 1,913 once invoked, about $0.0005 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 skills, from other repositories
bootstrap-repo-analysis
First-time analysis of a repository with no prior reviewer outcomes. Crawl historical merged-PR review feedback with the gh CLI (plus any preloaded samples), extract the team's review norms, and synthesize the initial per-repo review-style prompt. Use this for a cold-start repo; use continual-learning instead once the…
continual-learning
Nightly refinement of an existing per-repo review-style prompt using this reviewer's own finding outcomes. Read confirmed (resolved-by-commit / thumbs-up) and dismissed (thumbs-down) findings, promote the bug patterns the team actually fixes, demote the false-positive patterns, reconcile against the current prompt…
secure-code-review
Use this skill when reviewing or writing code that handles user input, authentication, file I/O, network requests, or database queries. Always check for common security vulnerabilities before considering the code complete.
pr-review
Review a GitHub pull request and post one formal review — advance the existing discussion and give precision-first, high-signal feedback. Judgement on the diff, not a build gate — CI validates that it builds, and a targeted probe is allowed as evidence. Use when asked to review a PR or on a cron PR scan.
coding
Use when five specialized coding agents (linter, perf, refactor, security, test) that enforce quality gates across the development lifecycle. From lint enforcement through performance profiling, refactoring, security auditing, and test coverage. Use when working with coding agents.
comment-review
A code-comment review tool that checks comments against a project's comment policy. It can also correct comments that do not meet the policy.