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 fledgeling-co/fledgeling-plugins/plugin install ship-featureWrote 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/fledgeling-co/fledgeling-plugins/ship-feature)<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.
<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>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.00214 | $0.03936 |
| Opus 5.5 | $0.00086 | $0.01574 |
| Sonnet 5.5 | $0.00043 | $0.00787 |
| Haiku 4.5 | $0.00021 | $0.00394 |
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.
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.
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.
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.
- 1mo ago Changed · -5 lines · +2 tokens per session f066e06190c2
- 1mo ago First seen · 250 lines · 212 tokens per session scan A 05490a16e518
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.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…