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/shravan-swagwalapm/shipstack/ship-featurenpx skills add shravan-swagwalapm/shipstack --skill ship-featuregit clone --depth 1 https://github.com/shravan-swagwalapm/shipstackWrote 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/shravan-swagwalapm/shipstack/ship-feature)<a href="https://agentmods.dev/skills/shravan-swagwalapm/shipstack/ship-feature"><img src="https://agentmods.dev/badge/skills/shravan-swagwalapm/shipstack/ship-feature.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.00037 | $0.01578 |
| Opus 5 | $0.00018 | $0.00789 |
| Sonnet 5 | $0.00007 | $0.00316 |
| Haiku 4.5 | $0.00004 | $0.00158 |
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 5d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ship-feature — Full Pipeline Orchestrator
Read and follow skills/shipstack/_preamble.md before proceeding.
You are orchestrating the complete feature pipeline. This skill chains superpowers (design, planning, execution) with ShipStack (scope, review, knowledge capture) in a single flow with 5 user gates.
Announce: "Using /ship-feature to run the full pipeline: design → scope → plan → build → review → ship → learn."
Flow Overview
GATE 1: DESIGN (Superpowers brainstorming + ShipStack vault)
GATE 2: SCOPE (ShipStack /challenge)
GATE 3: PLAN (Superpowers writing-plans + ShipStack /review-plan)
GATE 4: BUILD+REVIEW (Superpowers subagent-driven-dev + ShipStack /review)
GATE 5: SHIP (ShipStack /ship-check)
AUTO: LEARN (ShipStack /retro)
GATE 1: DESIGN
Invoke the superpowers:brainstorming skill via the Skill tool.
CRITICAL OVERRIDE: When brainstorming completes and the spec is written + approved by the user, do NOT invoke writing-plans. The brainstorming skill says "The terminal state is invoking writing-plans" — ignore that instruction. Instead, return here and proceed to Gate 2.
The vault context loaded by the preamble ($PAST_MISTAKES, $DECISIONS, $LAST_SESSION) is already in your conversation. Superpowers brainstorming will benefit from it automatically — reference past mistakes and decisions when they're relevant during the design discussion.
Artifact produced: docs/superpowers/specs/YYYY-MM-DD-<feature>-design.md
Store the spec path as $SPEC_PATH — downstream gates need it.
Gate: After spec is written, self-reviewed, and user-approved → proceed to Gate 2.
GATE 2: SCOPE
Invoke the ShipStack /challenge skill via the Skill tool.
Tell the challenge skill: "The design doc is at $SPEC_PATH" so it reads the correct file (superpowers writes to docs/superpowers/specs/, not ~/.shipstack/projects/$SLUG/designs/).
The challenge skill will:
- Ask the user to choose a scope mode (EXPAND / SELECTIVE EXPAND / HOLD / REDUCE)
- Run temporal interrogation (what decisions now vs. during implementation?)
- Build an error & rescue map
- Write scope decisions to vault
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.
- 5d ago First seen · 158 lines · 37 tokens per session scan A a046dcf11ceb
ship-feature is a skill published in the GitHub repository shravan-swagwalapm/shipstack (19 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 1,578 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…