Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Acendas/shipyard/plugin install shipyardWrote 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/acendas/shipyard/ship-review)<a href="https://agentmods.dev/skills/acendas/shipyard/ship-review"><img src="https://agentmods.dev/badge/skills/acendas/shipyard/ship-review.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.00013 | $0.19308 |
| Opus 5 | $0.00006 | $0.09654 |
| Sonnet 5 | $0.00003 | $0.03862 |
| Haiku 4.5 | $0.00001 | $0.01931 |
Grade A, and why
ship-review scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Live-capture the dev server and E2E runs.** Anything you run here to observe behavior (dev server startup logs, E2E runner output, `curl` sanity checks against the running app) goes through `shipyard-logcap run <name> How it starts
The opening of the file, as written. The whole thing — 715 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shipyard: Review & Verification
Verify completed work against spec. Auto-test, screenshot, demo to user, get approval.
Context
!shipyard-context review-context
Onboarding gate. If the bundled context contains SHIPYARD_ONBOARDING_REQUIRED=true, run the exact SHIPYARD_ONBOARDING_COMMAND once with Bash, report the CLI output to the user, and STOP. Do not infer setup state by reading or writing Shipyard state files; onboarding decisions are CLI-owned.
Paths. All Shipyard file ops use the absolute SHIPYARD_DATA prefix from the context block (no ~, $HOME, or shell variables). Bash is for project tests, git, and the shipyard-data CLI (cursor/sprint mutations, metrics, and archive-sprint). Never cd into the data directory before running shipyard-data commands — they resolve the data directory internally via git and env vars; cd-ing into a non-git directory breaks the resolver. Never use echo, printf, or shell redirects (>) to write state files.
The pipeline cursor, PROGRESS.md, and HANDOFF.md are CLI-owned — the model never writes them. A PreToolUse hook DENIES any Write/Edit targeting REVIEW-CURSOR.md, PROGRESS.md, or HANDOFF.md. The only writer is the shipyard-data cursor CLI, which validates the stage transition against the stage graph, runs the terminal-evidence gate + stale-cycle guard in-process (exit 3 with reasons on failure), appends the pipeline event atomically with the cursor write, re-renders PROGRESS.md, and prints the tick/terminal marker lines itself (stop marker guaranteed LAST). So: advance a tick with shipyard-data cursor advance review <stage> [k=v ...] [--note "<narrative>"]; do NOT emit pipeline_tick_completed/pipeline_terminal yourself and do NOT print your own ▶ TICK COMPLETE/▶ CYCLE COMPLETE markers — echo the CLI's output as the final lines of the tick. SPRINT.md frontmatter is mutated via shipyard-data sprint set <key> <value> (never a model Edit). Verdict files (verify/<F>-verdict.md) and other narrative artifacts stay model Writes. Use the Write tool (auto-approved for SHIPYARD_DATA) for those. When passing paths into spawned Agent prompts, substitute the literal SHIPYARD_DATA path.
What ships with it
6 files 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.
- 7d ago First seen · 715 lines · 13 tokens per session scan A fb151a0c04f3
ship-review is a skill published in the GitHub repository Acendas/shipyard (2 stars, last pushed 25d ago), licensed MIT. It adds 13 tokens to every session and 19,308 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
code-review-loop
Use when opening a PR for review or when receiving review feedback. Activate for keywords like "code review", "PR review", "request review", "review feedback", "address comments", "reviewer said". Covers both ends of the loop: preparing a reviewable PR and acting on feedback rigorously. Always engage with every…
release-and-changelog
Use when cutting a release, bumping a version, or writing release notes. Activate for keywords like "release", "version bump", "changelog", "release notes", "tag", "publish", "ship a release", "v1.x", "v2.x". Enforces version hygiene: SemVer respect, changelog discipline, atomic commits, tagged release. Always reflect…
seal
Ships a feature — simplify pass, certify, commit, PR, CI monitoring, review loop, merge. Use when a feature branch is verified and ready to ship.
int-github-review
Review GitHub repos — open PRs, community issues, stars/forks, releases, contributors. Use when user says 'check github', 'github review', 'repo status', 'open PRs', 'github issues', 'repository status', or any reference to checking GitHub repos status.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.