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 fledgeling-co/fledgeling-plugins/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/fledgeling-co/fledgeling-plugins/shipyard)<a href="https://agentmods.dev/skills/fledgeling-co/fledgeling-plugins/shipyard"><img src="https://agentmods.dev/badge/skills/fledgeling-co/fledgeling-plugins/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/fledgeling-co/fledgeling-plugins/shipyard"><img src="https://agentmods.dev/badge/skills/fledgeling-co/fledgeling-plugins/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.00127 | $0.00885 |
| Opus 5.5 | $0.00051 | $0.00354 |
| Sonnet 5.5 | $0.00025 | $0.00177 |
| Haiku 4.5 | $0.00013 | $0.00089 |
Grade A, and why
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 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shipyard — the map
Seven stage skills take a feature from rough idea to independently verified code. This skill is the router: say which stage fits, and point at the shared canon. It never performs a stage itself.
Running as a Gemini model? Read gemini.md in this directory first, then follow this file with the overrides it names. It turns this map's counts — seven stages, eight statuses, nine canon files — into a ledger an answer must fill, and makes the routing read the reference files rather than recall them, because a router is one sentence away from performing the stage it should be handing over. Other models skip it.
The stages, and when each is the one you want
| You have | Run | It produces |
|---|---|---|
| A rough idea ("an app that does X") | shipyard:intake |
Briefs in docs/features-to-triage/, plus separable AI-proposed companions |
| A brief or ticket needing a readiness check | shipyard:triage |
The verdict + assumptions → status To Do, or Needs More Info with essential questions |
| A triaged feature needing its build plan | shipyard:plan |
A committed docs/plans/<id>.md with a test strategy → Ready for AI |
| A user-facing feature needing its UI settled | shipyard:design |
All-platform mocks + a state matrix, gated by design-review and be-my-witness |
| A planned feature ready to build | shipyard:work |
The branch in .worktrees/<ID> with evidence tables → Developer Review |
| A built feature awaiting grading | shipyard:verify |
A cross-family verdict against the running app → Done or Needs More Work |
| A failed verdict or a QA gap list | shipyard:gap-fix |
The gaps closed in code → back to Developer Review for re-verification |
For a whole feature end to end, use the ship-feature:ship-feature conductor; for a backlog, ship-fleet:ship-fleet;
for a portfolio, ship-armada:ship-armada. Prefer a conductor whenever the goal is a finished feature
rather than one stage's artifact.
The status machine (one enum, complete)
What ships with it
1 file 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.
- 1mo ago Changed · +3 tokens per session ef34ee38624a
- 1mo ago First seen · 53 lines · 124 tokens per session scan A daeacb686ee8
shipyard is a skill published in the GitHub repository fledgeling-co/fledgeling-plugins (2 stars, last pushed 4d ago), licensed MIT. It adds 127 tokens to every session and 885 once invoked, about $0.0005 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-04.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…