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-reviewgit 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-review)<a href="https://agentmods.dev/skills/bonnguyenitc/specship/ss-review"><img src="https://agentmods.dev/badge/skills/bonnguyenitc/specship/ss-review/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-review"><img src="https://agentmods.dev/badge/skills/bonnguyenitc/specship/ss-review.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.00074 | $0.02885 |
| Opus 5.5 | $0.00030 | $0.01154 |
| Sonnet 5.5 | $0.00015 | $0.00577 |
| Haiku 4.5 | $0.00007 | $0.00288 |
Grade A, and why
ss-review 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 2mo 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review
Goal: take a change from "code written" to "ready to ship" — verified correct, clean, and consistent with the spec, before it's committed.
When to use
- Implementation is finished (ideally via the
ss-codingskill). - You're asked to review, wrap up, finalize, or check if a change is merge-ready.
- Final stage of the workflow: spec → plan → coding → review (+
debug).
Shared task state
Part of the task pipeline — see ../WORKFLOW.md for the full contract.
- Hydrate: resolve the active
TASK-<ID>, readtasks/TASK-<ID>/task.md,spec.md,plan.md,docs/onboarding/how-to-code.md, and the diff. - Checkpoint: write
review.mdand tick verifiedAC#inspec.md; updatetask.md— setreviewartifactchanges-requested/approved, setstage: done+status: doneonly when approved, bumpupdated:, append a Pipeline Log line carrying your agent label (format:../WORKFLOW.md→ Agent handoff). - Blocked? If the review can't complete because of an external dependency (a staging env, access, or sign-off it's waiting on), set
status: blocked, note it inBlocked by:, and log it; flip back toactivewhen it clears. A blocker defect found in review goes throughss-debug(which setsblockeditself).blockedis involuntary — to set the task aside by choice, usess-pause-task. See../WORKFLOW.md→ Status values. - Lessons: read
tasks/LESSONS.mdat hydrate and apply its rules; if you detect a process mistake (in this stage or an earlier one), fix it and append anL#entry there (see../WORKFLOW.md→ Lessons).
Method
0. Load the artifacts
Read the files the earlier stages produced so the review is grounded, not generic:
tasks/TASK-<ID>/spec.md— requirements, acceptance criteria, edge cases.tasks/TASK-<ID>/plan.md— the intended approach and steps.docs/onboarding/how-to-code.md+source-structure.md— the code-style and placement rules.
1. Review the diff — independent eyes for bugs, task-grounded eyes for fit
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.
- 2mo ago First seen · 118 lines · 74 tokens per session scan A 395225e81cdb
ss-review is a skill published in the GitHub repository bonnguyenitc/specship (2 stars, last pushed 3mo ago), licensed MIT. It adds 74 tokens to every session and 2,885 once invoked, about $0.0003 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.
ss-review compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| ss-reviewbonnguyenitc/specship | Skill | 2 | 3mo ago | MIT | A | 74 | Codex |
| reviewzhnt/loushang | Skill | 2.0k | yesterday | Apache-2.0 | A | 13 | Claude Code, Codex |
| pr-reviewnearform/lastlight | Skill | 44 | 2d ago | MIT | A | 69 | Claude Code, Codex |
| codingoyi77/1ai-skills | Skill | 17 | yesterday | MIT | A | 54 | Claude Code |
| code-reviewnearform/lastlight | Skill | 44 | 2d ago | MIT | A | 83 | Claude Code, Codex |
| pr-commentnearform/lastlight | Skill | 44 | 2d ago | MIT | A | 41 | Claude Code, Codex |
| comment-reviewopenkursar/hello-halo | Skill | 1.9k | yesterday | none | A | 46 | Claude Code, Codex |