ship-feature

ship-feature is a skill for Claude Code from fledgeling-co/fledgeling-plugins. It costs 214 tokens per session (3,936 once invoked), scanned A, original, MIT.

A workflow conductor for taking one feature from an idea or ticket to merged, verified production code. It coordinates separate stages such as planning, design, implementation, testing, and review.

In plain words
What is it for?
It coordinates intake, triage, planning, design, coding in a separate worktree, follow-up fixes, end-to-end testing, acceptance checks, and merging.
Why use it?
It keeps the feature's intent and evidence connected across stages, reducing the chance that work is merged before it has been properly checked.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions CLAUDE.md; mentions subagents; mentions Gemini CLI.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the ship-feature plugin — 1 skill shipped together

Good fit It coordinates intake, triage, planning, design, coding in a separate worktree, follow-up fixes, end-to-end testing, acceptance checks, and merging.

Compare 6 skills from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add fledgeling-co/fledgeling-plugins
Claude Code
/plugin install ship-feature

Made for: Claude Code.

Or install ship-feature, the plugin that ships this one along with the rest of its 1 skill.

Wrote 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.

agentmods badge for ship-feature

README.md
[![agentmods](https://agentmods.dev/badge/skills/fledgeling-co/fledgeling-plugins/ship-feature/github.svg)](https://agentmods.dev/skills/fledgeling-co/fledgeling-plugins/ship-feature)
Your own site
<a href="https://agentmods.dev/skills/fledgeling-co/fledgeling-plugins/ship-feature"><img src="https://agentmods.dev/badge/skills/fledgeling-co/fledgeling-plugins/ship-feature/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.

agentmods 80×15 button for ship-feature

Your own site · 80×15
<a href="https://agentmods.dev/skills/fledgeling-co/fledgeling-plugins/ship-feature"><img src="https://agentmods.dev/badge/skills/fledgeling-co/fledgeling-plugins/ship-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 214 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,936 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00214 $0.03936
Opus 5.5 $0.00086 $0.01574
Sonnet 5.5 $0.00043 $0.00787
Haiku 4.5 $0.00021 $0.00394

Measured 1mo ago against content hash f066e06190c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ship-feature 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.

plugins/ship-feature/skills/ship-feature/SKILL.md · 245 lines

How it starts

The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ship Feature — the end-to-end conductor

Take one feature from a bare description to merged, verified, production code by conducting the shipyard stage skills in sequence. You are the conductor: you hold the feature's intent from first read to final merge, invoke each stage skill, verify its artifact landed, carry the right context forward, and make the between-stage judgment calls no single stage can. You never re-implement a stage here — you run them and thread them together.

rough idea ──→ intake      briefs in docs/features-to-triage/ (+ proposed-by-ai siblings)
brief/ticket ─→ triage     readiness verdict + assumptions            → To Do
               plan  ──┐   committed docs/plans/<id>.md + test strategy → Ready for AI
               design ─┘   all-platform mocks + state matrix, review-gated   (parallel)
               work        build in .worktrees/<ID> on ai/<id>; evidence tables; targeted D′ follow-up if needed
                           → Developer Review
               4b loop     deferred / child specs — SAME branch
               gap-fix     close remaining gaps in code
               e2e         acceptance suite vs the branch, locally, green twice
               verify      cross-family acceptance vs the running app → Done | Needs More Work
               finalize    fail-closed gate → rebase → merge → push → cleanup

Canonical shared rules ride with the stage skills in the shipyard plugin's references/ (tracker adapter, model lanes, evidence rules, second-opinion lanes, operational rules). This skill's own references: references/orchestration-model.md (read first), references/deferred-work-loop.md, references/e2e-and-finalize.md.

Running as a Gemini model? Read gemini.md in this directory first, then follow this file with the overrides it names. It gives every categorical scope in the pipeline a denominator, turns the fourteen-box pre-merge gate into pasted command output with its prerequisite artifacts checked first, and makes each stage a real invocation whose file the next phase opens. Other models skip it.

Read the full file on GitHub · 245 lines

Files

What ships with it

4 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.

Changes

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.

  1. 1mo ago Changed · -5 lines · +2 tokens per session f066e06190c2
  2. 1mo ago First seen · 250 lines · 212 tokens per session scan A 05490a16e518

Subscribe to this mod's changes

ship-feature is a skill published in the GitHub repository fledgeling-co/fledgeling-plugins (2 stars, last pushed 4d ago), licensed MIT. It adds 214 tokens to every session and 3,936 once invoked, about $0.0009 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.