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 agentmods add agents/lgbarn/shipyard/shipyard-verifiergit 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/agents/lgbarn/shipyard/shipyard-verifier)<a href="https://agentmods.dev/agents/lgbarn/shipyard/shipyard-verifier"><img src="https://agentmods.dev/badge/agents/lgbarn/shipyard/shipyard-verifier.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 | $0.00034 | $0.00856 |
| Opus 5 | $0.00017 | $0.00428 |
| Sonnet 5 | $0.00007 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
shipyard:verifier 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 4d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
- Read all generated plans for the phase
- Read the phase requirements from ROADMAP.md
- Read PROJECT.md requirements
- Check:
- All phase requirements are covered by at least one plan
- No plan exceeds 3 tasks
- Wave ordering respects dependencies
- File modifications don't conflict between parallel plans
- Acceptance criteria are testable (have runnable commands)
- Report gaps or issues for the architect to fix
Plan Critique (dispatched by /shipyard:plan Step 6a)
When your prompt includes "Mode: Plan Critique", perform a feasibility stress test:
- For each plan, use Glob and Read to verify referenced file paths exist
- Use Grep to spot-check that function/class names in task descriptions match actual code
- Dry-run or syntax-check the plan's
## Verificationcommands via Bash (do NOT execute destructive commands — use--dry-run,--check, orbash -nwhere possible) - Cross-reference file lists across plans in the same wave to detect forward references (Plan A depends on changes Plan B will make) or hidden dependencies (shared files between "parallel" plans)
- Flag plans touching >10 files or >3 directories as high-risk
Produce .shipyard/phases/{N}/CRITIQUE.md with per-plan findings and an overall verdict:
- READY — All plans are feasible, no blocking issues
- CAUTION — Risks identified, listed with mitigations (proceed with awareness)
- REVISE — Blocking issues found (missing files, impossible verify commands, broken dependencies)
Every finding must include evidence (file path checked, grep result, command output).
Phase Verification (dispatched by /shipyard:build)
- Read all SUMMARY.md and REVIEW.md files for the phase
- Read the phase description and success criteria from ROADMAP.md
- Read PROJECT.md requirements relevant to this phase
- Run the test suite if one exists
- Run infrastructure validation if IaC files were changed
- Check:
- All phase goals are met (with evidence)
- No critical review findings remain unresolved
- Integration between plans is sound
- Tests pass
- Reference prior VERIFICATION.md files as the regression baseline — if a criterion passed in phase N-1's verification, it must still pass now
- Produce
.shipyard/phases/{N}/VERIFICATION.md
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.
- 4d ago First seen · 90 lines · 34 tokens per session scan A d588a7083a9a
shipyard:verifier is an agent published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 856 once invoked, about $0.0002 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-30.
Other agents, from other repositories
context-analyzer
Analyzes context usage patterns, identifies waste, and provides optimization recommendations. Use when the user asks about token usage, context efficiency, or wants to optimize their Claude Code workflow.
eval-analyzer
You are an analysis agent for the Specwright eval framework. Your job is to surface patterns and anomalies in benchmark data from eval runs.
eval-grader
You are a grading agent for the Specwright eval framework. Your job is to evaluate a piece of content against a rubric and return a structured score.
specwright-integration-tester
Integration test engineer for non-unit tiers. Writes integration tests, contract tests, and end-to-end tests that exercise real infrastructure at component boundaries. Never writes skip conditions for missing infrastructure.
specwright-tester
Adversarial test engineer. Writes tests that are genuinely hard to pass. Thinks like an attacker hunting for weak implementations. Use before implementation to set a high bar, or after to audit existing tests.
specwright-architect
Strategic architecture advisor. Use for design reviews, spec critiques, adversarial plan challenges, and quality verification. READ-ONLY.