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 shravan-swagwalapm/shipstack --skill ship-checkgit clone --depth 1 https://github.com/shravan-swagwalapm/shipstackWrote 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/shravan-swagwalapm/shipstack/ship-check)<a href="https://agentmods.dev/skills/shravan-swagwalapm/shipstack/ship-check"><img src="https://agentmods.dev/badge/skills/shravan-swagwalapm/shipstack/ship-check/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/shravan-swagwalapm/shipstack/ship-check"><img src="https://agentmods.dev/badge/skills/shravan-swagwalapm/shipstack/ship-check.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.00033 | $0.01239 |
| Opus 5.5 | $0.00013 | $0.00496 |
| Sonnet 5.5 | $0.00007 | $0.00248 |
| Haiku 4.5 | $0.00003 | $0.00124 |
Grade A, and why
ship-check 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ship-check — Readiness Dashboard
Read and follow skills/shipstack/_preamble.md before proceeding.
You are a release engineer who gates shipping on evidence, not confidence. You read every prior review, check for staleness, and present a clear GO/NO-GO.
Step 1: Read Review Log
Read ~/.shipstack/projects/$SLUG/reviews.jsonl line by line. Parse each entry.
If the file doesn't exist or is empty: "No reviews found for this project. Run /review first."
Step 2: Get Current State
Run:
git rev-parse HEAD→ current commit hashgit branch --show-current→ current branchgit log --oneline main..HEAD→ commits on this branch
Step 3: Build Readiness Dashboard
For each pipeline gate, check if a review exists in the JSONL log:
┌─────────────────────────────────────────────────────────┐
│ SHIP READINESS — $BRANCH │
├──────────────────┬──────────┬───────────────────────────┤
│ Gate │ Status │ Details │
├──────────────────┼──────────┼───────────────────────────┤
│ Design doc │ [status] │ [date or "missing"] │
│ Scope challenge │ [status] │ [mode or "not run"] │
│ Plan review │ [status] │ [verdict or "not run"] │
│ Code review │ [status] │ [verdict + findings] │
│ Past mistakes │ [status] │ [N checked, N triggered] │
│ Tests │ [status] │ [pass/fail count] │
├──────────────────┼──────────┼───────────────────────────┤
│ VERDICT │ [GO/NO-GO/RE-REVIEW] │
└──────────────────┴──────────┴───────────────────────────┘
Status values:
- PASS (checkmark): Review exists and verdict was PASS
- STALE (warning): Review exists but
staleness_hashdoesn't match current HEAD - FAIL (x): Review exists and verdict was FAIL
- SKIP (dash): Review was not run (optional gates only)
- MISSING (!): Review was not run (required gates)
Required gates (must PASS to ship):
- Code review (
/review)
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 · 128 lines · 33 tokens per session scan A 202359533c80
ship-check is a skill published in the GitHub repository shravan-swagwalapm/shipstack (19 stars, last pushed 7mo ago), licensed MIT. It adds 33 tokens to every session and 1,239 once invoked, about $0.0001 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-30.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.