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 lgbarn/shipyard --skill using-shipyardgit 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/skills/lgbarn/shipyard/using-shipyard)<a href="https://agentmods.dev/skills/lgbarn/shipyard/using-shipyard"><img src="https://agentmods.dev/badge/skills/lgbarn/shipyard/using-shipyard/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/lgbarn/shipyard/using-shipyard"><img src="https://agentmods.dev/badge/skills/lgbarn/shipyard/using-shipyard.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.00083 | $0.04388 |
| Opus 5.5 | $0.00033 | $0.01755 |
| Sonnet 5.5 | $0.00017 | $0.00878 |
| Haiku 4.5 | $0.00008 | $0.00439 |
Grade A, and why
using-shipyard 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 6d 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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Shipyard
What is Shipyard?
Shipyard is a structured project execution framework for Claude Code. It works as a plugin that helps you:
- Plan work in phases — break large projects into manageable pieces with clear success criteria
- Build with parallel agents and TDD — fresh 200k-token context per task, atomic commits, test-driven development
- Review code quality and security automatically — two-stage code review, OWASP security audits, complexity analysis
- Ship with confidence — verification gates, documentation generation, and delivery workflows
Shipyard works as a Claude Code plugin. Install it once, then use slash commands in any project.
Getting Started
New to Shipyard? Follow these steps:
/shipyard:init— Set up your project preferences (interaction mode, git strategy, quality gates). Takes ~1 minute./shipyard:brainstorm— Explore what you want to build through interactive dialogue. Captures a project definition./shipyard:plan 1— Plan your first phase of work. Researches the codebase and decomposes into executable tasks./shipyard:build— Execute the plan with parallel builder agents, review gates, and security audits./shipyard:ship— Verify, audit, document, and deliver your completed work.
For quick one-off tasks, skip the lifecycle and use /shipyard:quick 'description'.
I Want To...
| Goal | Command |
|---|---|
| Set up a new project | /shipyard:init |
| Explore requirements | /shipyard:brainstorm |
| Understand existing code | /shipyard:map |
| Plan a phase | /shipyard:plan [phase] [--skip-research] |
| Build from a plan | /shipyard:build [phase] [--plan N] [--light] |
| Quick one-off task | /shipyard:quick "task" |
| Review my code | /shipyard:review |
| Security check | /shipyard:audit |
| Research technology options | /shipyard:research "topic" |
| Find duplication/complexity | /shipyard:simplify [scope] |
| Generate documentation | /shipyard:document [scope] |
| Run tests and verify | /shipyard:verify [criteria] |
| Check progress | /shipyard:status |
| Change settings | /shipyard:settings |
| Rollback to checkpoint | /shipyard:rollback |
| Recover from errors | /shipyard:recover |
| Ship completed work | /shipyard:ship [--phase | --milestone | --branch] |
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.
- 6d ago Changed · +8 tokens per session 431e08999d10
- 1mo ago First seen · 280 lines · 75 tokens per session scan A a0b5496c8394
using-shipyard is a skill published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 6d ago), licensed MIT. It adds 83 tokens to every session and 4,388 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…
done-blocked
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.
outcome-roadmap
Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built.
pm-planning
Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria. The pipeline can only orchestrate work it can see; this skill defines what "seeable work" looks like.
protocol-tracker
Internal skill for commands. The tracker verb-resolution protocol - how a lets-tracker block resolves through the active adapter, the neutral read shape, body crossing, degradation, preflight and trust. Loaded by a command or skill right before its first tracker verb. Do not trigger on user conversation.