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-specgit 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)<a href="https://agentmods.dev/skills/lgbarn/shipyard/import-spec"><img src="https://agentmods.dev/badge/skills/lgbarn/shipyard/import-spec.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.1 | $0.00028 | $0.02103 |
| Opus 5 | $0.00014 | $0.01052 |
| Sonnet 5 | $0.00006 | $0.00421 |
| Haiku 4.5 | $0.00003 | $0.00210 |
Grade A, and why
import-spec 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 3d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipyard:import-spec - Import spec-kit Artifacts
You are executing the Shipyard spec-kit import workflow. This replaces /shipyard:brainstorm when you have already created a spec using spec-kit. Follow these steps precisely.
Step 1: Parse Argument
- If an argument is provided, use it as the feature path (e.g.,
specs/003-chat-system). - If no argument is provided, check if a
specs/directory exists in the project root.- If
specs/exists and contains subdirectories: useAskUserQuestionto present the available feature directories and ask the user to choose one. - If
specs/does not exist or is empty: tell the user: "No spec-kit feature directory found. Provide the path as an argument:/shipyard:import-spec specs/<feature-name>" and stop.
- If
Step 2: Validate Prerequisites
- Verify
.shipyard/directory exists. If not, tell the user to run/shipyard:initfirst, then stop. - Verify the feature path exists and contains
spec.md. Ifspec.mdis missing, tell the user: "spec.md not found in<feature-path>. Run/speckit.specifyfirst to generate the feature spec." and stop. - Inventory which artifacts exist — note which are present for use in later steps:
<feature-path>/spec.md(required)<feature-path>/plan.md(optional — used for ROADMAP.md generation)<feature-path>/research.md(optional — copied to phase RESEARCH.md)<feature-path>/data-model.md(optional — appended to RESEARCH.md)<feature-path>/contracts/directory (optional — summarized into RESEARCH.md)<feature-path>/tasks.md(optional — seeded into architect input at plan time).specify/memory/constitution.md(optional — added to PROJECT.md constraints)
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-kit import (Recommended)— overwrite PROJECT.md with the imported spec contentMerge — update requirements section only— keep existing PROJECT.md but replace the Requirements section with spec-kit user storiesCancel— stop
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.
- 3d ago First seen · 207 lines · 28 tokens per session scan A d0e83187730f
import-spec is a skill published in the GitHub repository lgbarn/shipyard (65 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 2,103 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
tasks
A task-breakdown tool that turns a plan, specification, feature brief, bug report, technical-debt item, or chore into small TASK-NNN work items. Technical debt means postponed cleanup or design work in a codebase.
roadmap
An implementation plan made from a technical specification, organized into phases, milestones, and dependencies.
continue
Autonomous work — find and execute ready tasks.
prd
A Product Requirements Document (PRD) writer for large software initiatives. A PRD records the problem, goals, requirements, assumptions, and evidence before implementation begins.
debt
A command for showing and closing unanswered questions attached to project documents such as requirements, specifications, features, and designs. It can show questions for the whole project or for one document.
missive
Invoke only when spawning a quest from a GitHub issue reference. Fetches GitHub issue context for quest spawning. Parses issue references, retrieves structured data via gh, and produces branch suggestions and PR keywords. Used standalone or as input to quest orchestration.