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 skills add Heyvhuang/ship-faster --skill workflow-feature-shippergit clone --depth 1 https://github.com/Heyvhuang/ship-fasterWrote 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/heyvhuang/ship-faster/workflow-feature-shipper)<a href="https://agentmods.dev/skills/heyvhuang/ship-faster/workflow-feature-shipper"><img src="https://agentmods.dev/badge/skills/heyvhuang/ship-faster/workflow-feature-shipper/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/heyvhuang/ship-faster/workflow-feature-shipper"><img src="https://agentmods.dev/badge/skills/heyvhuang/ship-faster/workflow-feature-shipper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00106 | $0.00931 |
| Opus 5 | $0.00053 | $0.00465 |
| Sonnet 5 | $0.00021 | $0.00186 |
| Haiku 4.5 | $0.00011 | $0.00093 |
Grade A, and why
workflow-feature-shipper 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 10d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Shipper
Turn "I want to build a feature" into a fast execution chain.
Input (Pass Paths Only)
feature.md: Requirements description (acceptance criteria + non-goals)repo_rootrun_dir
Optional flags (recommended inside feature.md)
mode:plan-only|execute(default:execute)feature_slug: short slug for artifact naming (default: derived from title + timestamp)quality_bar:demo-ready|functional-only(default:demo-readyfor user-facing UI features)
Output (Persisted)
evidence/features/<feature_slug>-plan.md(checklist plan: tasks + verification)evidence/parallel/features/<feature_slug>/(if implementation is split)evidence/features/<feature_slug>-summary.md
Process
- Hooks doctor (required check; non-blocking): Run
tool-hooks-doctoronce at the start of the session to verifyskill-evolutionhooks are enabled. If missing, offer to install project-level hooks; continue either way. - Read
feature.md, normalize into: acceptance criteria, boundaries, risks, rollback. - Prototype UI rule (default): if this feature affects user-facing UI and
quality_barisn’tfunctional-only, propose 1 “demo moment” (animation/micro-interaction) and add it to acceptance criteria. Must respectprefers-reduced-motion. - Produce 2 options (A: minimal; B: cleaner but slower), default to A. If user cares about “demo feel”, offer A-demo-ready vs A-functional-only as explicit sub-options.
- Split into PR-sized small steps (each independently runnable + rollback-able).
- Write plan to
evidence/features/<feature_slug>-plan.md. - If
mode: plan-only, stop here and ask for confirmation before implementing. - Implement (batch execution + checkpoints):
- UI visual/layout/animation changes → First call
tool-design-style-selectorto load the project’sdesign-system.md, then strictly follow it. Iftool-ui-ux-pro-maxis installed, use it to ground motion/UX constraints (search “animation” + “accessibility”). For complex visual/animation/responsive design, delegate to/geminifrontend UI/UX senior design agent. - Business logic/data flow/integration → Implement directly.
- Default batch rhythm: 3 small tasks per batch → run verification → report and wait for feedback; stop immediately for help when blocked/verification fails.
- After each batch (or before merge), recommend using
review-qualityfor a conclusive review + verdict.review-qualityis the single entry point and will auto-triage: if React/Next.js performance risk is detected, it will also runreview-react-best-practices.- If the user explicitly wants only a React/Next.js perf audit, run
review-react-best-practicesdirectly.
- UI visual/layout/animation changes → First call
- Verification: can run, can build (and existing tests pass).
- If verification fails (tests/build/runtime error): run
tool-systematic-debuggingbefore attempting more fixes. - Persist debugging artifacts to:
evidence/features/<feature_slug>-debug.md(repro steps, hypotheses, root cause, fix + re-verify)
- If verification fails (tests/build/runtime error): run
- Write
evidence/features/<feature_slug>-summary.md: what was done, how verified, next steps. - Wrap up: Do a
skill-evolutionEvolution checkpoint (3 questions); if user chooses "want to optimize", runskill-improverbased on thisrun_dirto produce minimal patch suggestions
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.
- 10d ago First seen · 55 lines · 106 tokens per session scan A 2034773e5904
workflow-feature-shipper is a skill published in the GitHub repository Heyvhuang/ship-faster (339 stars, last pushed 25d ago), licensed MIT. It adds 106 tokens to every session and 931 once invoked, about $0.0005 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
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
dashboard-widgets
Author a dashboard widget — a small React component backed by named LangWatchQL queries — from a plain question. Discovers the analytics schema, writes the queries, writes the widget file, saves it, then proves it renders. Use when asked to build, prototype, or iterate on a custom chart widget, or to add a widget…
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…