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 import-spec-filegit 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/import-spec-file)<a href="https://agentmods.dev/skills/lgbarn/shipyard/import-spec-file"><img src="https://agentmods.dev/badge/skills/lgbarn/shipyard/import-spec-file/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/import-spec-file"><img src="https://agentmods.dev/badge/skills/lgbarn/shipyard/import-spec-file.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.02617 |
| Opus 5.5 | $0.00013 | $0.01047 |
| Sonnet 5.5 | $0.00006 | $0.00523 |
| Haiku 4.5 | $0.00003 | $0.00262 |
Grade A, and why
import-spec-file 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:import-spec-file - Import Handwritten Spec Document
You are executing the Shipyard spec-file import workflow. This is the path for handwritten, freeform, or pre-existing specification documents — use this instead of /shipyard:brainstorm when a spec already exists in a non-spec-kit format. Follow these steps precisely.
Step 1: Parse Argument
- If an argument is provided, treat it as the spec file path. Resolve relative paths from the project root (cwd). Absolute paths are used as-is.
- If no argument is provided, check for common spec file patterns in the project root and one level deep:
- Files matching
*spec*.md,*SPEC*.md,*requirements*.md,*design*.md - If exactly one match: offer to use it. Ask: "Found
<path>. Use this as the spec?" - If multiple matches: use
AskUserQuestionto present the matches and ask the user to select one. - If no matches: tell the user: "No spec file found. Provide the path as an argument:
/shipyard:import-spec-file path/to/spec.md" and stop.
- Files matching
Step 2: Validate Prerequisites
- Verify
.shipyard/directory exists. If not, tell the user to run/shipyard:initfirst, then stop. - Verify the spec file exists and is readable. If not, tell the user: "Spec file not found:
<path>" and stop. - Note the spec file's filename, directory, and size (line count) for use in later steps.
Step 3: Check Existing PROJECT.md
If .shipyard/PROJECT.md already exists, use AskUserQuestion to ask:
"A project definition already exists in
.shipyard/PROJECT.md. What would you like to do?"
Replace with spec import (Recommended)— overwrite PROJECT.md with content derived from the specMerge — update requirements section only— keep existing PROJECT.md but replace the Requirements section with content from the specCancel— stop
Step 4: Read, Analyze, and Interview
Read the full spec file. Then analyze its structure to identify the following sections (the document may use any section names — use judgment to identify the semantic equivalent):
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 · +2 tokens per session fac05f2e9a74
- 1mo ago First seen · 219 lines · 30 tokens per session scan A 634ba2490330
import-spec-file is a skill published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 6d ago), licensed MIT. It adds 32 tokens to every session and 2,617 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-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.