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 Acendas/shipyard/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/acendas/shipyard/ship-sprint)<a href="https://agentmods.dev/skills/acendas/shipyard/ship-sprint"><img src="https://agentmods.dev/badge/skills/acendas/shipyard/ship-sprint.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.00014 | $0.11054 |
| Opus 5 | $0.00007 | $0.05527 |
| Sonnet 5 | $0.00003 | $0.02211 |
| Haiku 4.5 | $0.00001 | $0.01105 |
Grade A, and why
ship-sprint 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 — 514 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shipyard: Sprint Planning
Plan a new sprint by pulling features from the backlog and decomposing into waves.
Context
!shipyard-context sprint-planning
Paths. All Shipyard file ops use the absolute SHIPYARD_DATA prefix from the context block (no ~, $HOME, or shell variables). Shipyard binaries you may invoke from Bash: shipyard-data archive-sprint <id>, shipyard-data metrics ..., shipyard-data init-sprint <id> (Step 12), shipyard-data draft set-sprint-status ..., shipyard-data sprint set <key> <value> and shipyard-data sprint check (Step 12). Never cd into the data directory before running shipyard-data commands — they resolve the data directory internally via git and env vars; cd-ing into a non-git directory breaks the resolver. Just run the command bare from the project root. Never use echo, printf, or shell redirects (>) to write state files. SPRINT.md and PROGRESS.md are created by the init-sprint CLI (template-canonical); SPRINT.md frontmatter is thereafter mutated only via shipyard-data sprint set, never a hand Edit (hand-editing frontmatter is the corruption class that welds keys together). PROGRESS.md and the pipeline cursors are CLI/render-owned — the model never writes them (a PreToolUse hook denies such writes). Metrics are CLI-owned: memory/metrics.json is authoritative and memory/metrics.md is generated; never Write/Edit either metrics file by hand. Use the Write tool (auto-approved for SHIPYARD_DATA) for arbitrary narrative artifacts (feature files, task files, SPRINT-DRAFT.md); the SPRINT.md body (Goal, ### Wave N, Critical Path, Risks, Swap Log) stays a model Edit on the CLI-created file. When passing paths into spawned Agent prompts, substitute the literal SHIPYARD_DATA path.
Onboarding gate. If the bundled context contains SHIPYARD_ONBOARDING_REQUIRED=true, run the exact SHIPYARD_ONBOARDING_COMMAND once with Bash, report the CLI output to the user, and STOP. Do not infer setup state by reading or writing Shipyard state files; onboarding decisions are CLI-owned.
What ships with it
10 files 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.
- references/carry-over-scan.md 8.1 KB
- references/implementation-decisions.md 8.1 KB
- references/planning-checklists.md 6.6 KB
- references/quality-manifest.md 3.6 KB
- references/spec-validation.md 19 KB
- references/sprint-analyst-report.md 3.0 KB
- references/task-decomposition-patterns.md 11 KB
- references/task-kinds.md 12 KB
- references/task-tech-notes-template.md 3.0 KB
- references/wave-decomposition.md 16 KB
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 First seen · 514 lines · 14 tokens per session scan A 13b8397c0aa0
ship-sprint is a skill published in the GitHub repository Acendas/shipyard (2 stars, last pushed 24d ago), licensed MIT. It adds 14 tokens to every session and 11,054 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-08-31.
Other skills, from other repositories
break-complex-projects-into-milestones
How to use AI to generate structured Work Breakdown Structures (WBS), 4-week critical path roadmaps, and verifiable milestone deliverables.
iterate-step-by-step
How to use the 4-Turn Conversational Scaffolding framework to build complex code, strategy, and content incrementally without token exhaustion or quality degradation.
write-epic
Produces a complete epic definition following Atlassian agile guidance. An epic captures a large initiative that is too big for a single sprint and must be decomposed into user stories.
write-user-story
Produces a complete, ready-to-groom user story following the standard Atlassian/agile format. It applies the INVEST criteria and the 3 Cs framework (Card, Conversation, Confirmation) to ensure each story is well-scoped, valuable, and testable — not just syntactically correct.
engenharia-de-requisitos
Use when doing requirements engineering, business analysis, or the software-engineering stage of discovering / specifying / validating / managing requirements — the stage BEFORE code (what to build) and AFTER (was the right thing built?), for new projects and for evolutions of existing ones. Triggers (EN)…
engenharia-de-requisitos
Use when doing requirements engineering, business analysis, or the software-engineering stage of discovering / specifying / validating / managing requirements — the stage BEFORE code (what to build) and AFTER (was the right thing built?), for new projects and for evolutions of existing ones. Triggers (EN)…