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 agentmods add skills/acendas/shipyard/ship-executenpx skills add Acendas/shipyard --skill ship-executegit clone --depth 1 https://github.com/Acendas/shipyardWhat 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 | $0.00013 | $0.23103 |
| Opus 5 | $0.00006 | $0.11551 |
| Sonnet 5 | $0.00003 | $0.04621 |
| Haiku 4.5 | $0.00001 | $0.02310 |
Grade A, and why
ship-execute 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 2d 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 — 596 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shipyard: Sprint Execution
Execute sprint tasks following the wave plan. Every task follows Red → Green → Refactor → Mutate.
Context
!shipyard-context sprint-execution
Paths. All Shipyard file ops use the absolute SHIPYARD_DATA prefix from the context block (no ~, $HOME, or shell variables). Bash is for project test commands, git, and shipyard-data CLI calls. Never cd into the data directory before running shipyard-data — the CLIs resolve the data directory internally via git and env vars, and cd-ing into a non-git directory breaks the resolver. Never use echo, printf, or shell redirects (>) to write state files — use the Write tool for the non-cursor data-dir files it still owns (auto-approved for SHIPYARD_DATA). 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.
Render before asking. Before every AskUserQuestion, render the decision context — the scenarios, concrete examples, tradeoffs, and any verbatim content being approved — as chat text; the tool call then carries only the short question and option labels. A bare AskUserQuestion with no rendered context above it is a bug (the window is too small to carry a real decision). Rendered means printed as assistant chat text in THIS response — content that only exists in a Read result, a subagent/Agent return, a capture file, an event-log entry, or the AskUserQuestion question/option strings does not count as rendered (the UI shows a compact card).
Quiet by default. Between user-input gates, work quietly — run tools, CLI calls, and dispatch bookkeeping without narrating them. Only three things reach the chat outside a gate: a one-line transition marker per boundary (stage / wave), the compact wave/progress bar, and a one-line banner when launching or receiving long-running background work. Findings and analysis are rendered in full ONLY at a gate (render-before-ask) or a terminal summary — between gates they collapse to a one-line result. Subagent returns are internal contracts: parse the structured fields, do not paste any preamble/epilogue/freeform commentary into chat. No running commentary ("Now I'll…", "Let me…", explaining a no-input step, re-narrating a tool result). Full doctrine: ${CLAUDE_PLUGIN_ROOT}/skills/ship-discuss/references/communication-design.md § "Interim Communication: Quiet by Default".
What ships with it
8 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.
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.
- 2d ago First seen · 596 lines · 13 tokens per session scan A bbef822a83ef
ship-execute is a skill published in the GitHub repository Acendas/shipyard (2 stars, last pushed 20d ago), licensed MIT. It adds 13 tokens to every session and 23,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-08-31.
Other skills, from other repositories
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)…
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.
backlog-grooming
Review Agiflow Planning tasks for readiness, prioritize approved work, group related tasks into work units, and promote ready tasks to Todo. Use when grooming a backlog, organizing planned tasks, creating work units, or deciding what should be executed next.
project-plan
Turn a product goal or feature request into a clear Agiflow project plan with small, testable tasks in Planning status. Use when starting a project, decomposing a feature, clarifying requirements, or converting an idea into an actionable backlog.