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 commands/lgbarn/shipyard/doctorgit 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/doctor)<a href="https://agentmods.dev/commands/lgbarn/shipyard/doctor"><img src="https://agentmods.dev/badge/commands/lgbarn/shipyard/doctor.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.00007 | $0.00794 |
| Opus 5 | $0.00003 | $0.00397 |
| Sonnet 5 | $0.00001 | $0.00159 |
| Haiku 4.5 | $0.00001 | $0.00079 |
Grade A, and why
doctor 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 5d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:doctor — Plugin Health Check
You are executing the Shipyard doctor diagnostic. Follow these steps precisely.
Step 1: Check Dependencies
Run each check and record pass/fail:
# 1. jq installed
command -v jq >/dev/null 2>&1 && echo "PASS: jq found ($(jq --version))" || echo "FAIL: jq not found — install with: brew install jq (macOS) or apt install jq (Linux)"
# 2. git installed
command -v git >/dev/null 2>&1 && echo "PASS: git found ($(git --version))" || echo "FAIL: git not found"
# 3. gh CLI (optional)
command -v gh >/dev/null 2>&1 && echo "PASS: gh found ($(gh --version | head -1))" || echo "INFO: gh not found — optional, needed for PR workflows"
Step 2: Check Plugin Structure
Verify the Shipyard plugin files are intact:
# Check plugin root has expected files
PLUGIN_ROOT="$(cd "$(dirname "$(readlink -f "$0" 2>/dev/null || echo "$0")")/.." && pwd)"
Verify these exist:
plugin.json— Plugin manifesthooks/— Hook scripts directoryscripts/— Script filesskills/— Skill definitionscommands/— Command definitions
Report any missing items.
Step 3: Check Skills Discoverable
# Count discoverable skills
skill_count=$(find skills/ -name "SKILL.md" -maxdepth 2 2>/dev/null | wc -l | tr -d ' ')
echo "Skills discovered: ${skill_count}"
List all discovered skills by name.
Step 4: Check Hooks Registered
Read plugin.json and verify hooks are defined:
SessionStarthook →scripts/state-read.shPreToolUsehooks (if any)PostToolUsehooks (if any)
Verify each hook script file exists and is executable.
Step 5: Check Project State (if .shipyard/ exists)
If .shipyard/ exists:
- Verify
.shipyard/is NOT a symlink - Check
STATE.jsonexists and is valid JSON with required fields (schema,phase,status) - Check
config.jsonexists and is valid JSON - Check
HISTORY.mdexists - Report any missing or corrupt files
If .shipyard/ does not exist:
"No Shipyard project in current directory. Run
/shipyard:initto set up."
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.
- 5d ago First seen · 115 lines · 7 tokens per session scan A f3db93997e26
doctor is a command published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 794 once invoked, about $0.0000 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 commands, from other repositories
sw-doctor
Read-only installation health check with repair hints.
sw-guard
Detect stack and configure deterministic guardrails.
sw-init
Project setup. Creates constitution and charter. Configures gates.
sw-status
Show current Specwright state and progress.
sw-ship
Strategy-aware merge via pull request. If branch-head freshness blocks and policy is rebase or merge, recover in the same run; manual is the fallback and still reruns /sw-verify before /sw-ship.
sw-verify
Interactive quality gates. Shows findings and validates against the spec. If branch-head freshness blocks and policy is rebase or merge, recover in the same run; manual is the fallback and stays on /sw-verify.