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.
git clone --depth 1 https://github.com/lgbarn/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/commands/lgbarn/shipyard/verify)<a href="https://agentmods.dev/commands/lgbarn/shipyard/verify"><img src="https://agentmods.dev/badge/commands/lgbarn/shipyard/verify/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/commands/lgbarn/shipyard/verify"><img src="https://agentmods.dev/badge/commands/lgbarn/shipyard/verify.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.00014 | $0.00557 |
| Opus 5.5 | $0.00006 | $0.00223 |
| Sonnet 5.5 | $0.00003 | $0.00111 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
verify 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 1mo 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:verify - On-Demand Verification
You are executing on-demand verification. Follow these steps precisely.
Step 1: Parse Arguments
Extract from the command:
criteria(optional): What to verify. Accepts:- No argument: Run project test suite and report results
- File path (e.g.,
acceptance-criteria.md): Verify each criterion in the file - Phase number (e.g.,
3): Verify phase success criteria from ROADMAP.md - Inline criteria (e.g.,
"all API endpoints return JSON"): Verify specific criteria
Step 2: Detect Context
- Check if
.shipyard/exists (optional — this command works anywhere). - If
.shipyard/config.jsonexists, readmodel_routing.validationfor model selection. - Otherwise, use default model: haiku.
- Follow Worktree Protocol (see
docs/PROTOCOLS.md) — detect worktree context.
Step 3: Build Agent Context
Assemble context per Agent Context Protocol (see docs/PROTOCOLS.md):
- The criteria to verify from Step 1
.shipyard/PROJECT.md(if exists).shipyard/ROADMAP.md(if phase number provided)- Test framework configuration (package.json scripts, Makefile targets, etc.)
- Working directory, current branch, and worktree status
Step 4: Dispatch Verifier
Dispatch a verifier agent (subagent_type: "shipyard:verifier") with:
- Follow Model Routing Protocol — resolve model from
model_routing.validation(default: haiku) - max_turns: 15
- All context from Step 3
- Instruction: For each criterion, identify how to verify it (test command, code inspection, manual check), execute verification, and record PASS or FAIL with concrete evidence
Step 5: Present Results
Display the verification report to the user.
If failures exist, offer follow-up:
"Would you like me to:
- Fix the failing criteria
- Run a more detailed review (
/shipyard:review)- Check security on the verified code (
/shipyard:audit)"
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.
- 1mo ago First seen · 65 lines · 14 tokens per session scan A 61ee98ac6599
verify is a command published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 10d ago), licensed MIT. It adds 14 tokens to every session and 557 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 commands, from other repositories
octo-deliver
Delivery phase - Review, validate, and test with multi-AI quality assurance.
tdd
Test-driven development with tests that actually catch breaks: red before green, name the break each test catches, and the mutation check before done.
test
Run the repository's actual test suite: every ecosystem's canonical runner — NOT run is never green.
ia-verify
Run pre-PR verification chain: build, types, lint, tests, security scan, diff review.
ia-test-browser
Run browser tests on pages affected by current PR or branch.
bugfix
TDD-driven bugfix workflow: tester writes failing test (RED) → developer fixes (GREEN) → developer refactors (REFACTOR) → reviewer validates. Accepts issue number, description, or both. Asks before pushing and creating a PR; --no-pr commits locally without asking.