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-ship-fastergit 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-ship-faster)<a href="https://agentmods.dev/skills/heyvhuang/ship-faster/workflow-ship-faster"><img src="https://agentmods.dev/badge/skills/heyvhuang/ship-faster/workflow-ship-faster/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-ship-faster"><img src="https://agentmods.dev/badge/skills/heyvhuang/ship-faster/workflow-ship-faster.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 62 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00109 | $0.03145 |
| Opus 5 | $0.00055 | $0.01572 |
| Sonnet 5 | $0.00022 | $0.00629 |
| Haiku 4.5 | $0.00011 | $0.00314 |
Grade A, and why
workflow-ship-faster 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 11d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow: Ship Faster (Next.js 16.1.1)
The goal of this chain is: Ship an idea or small prototype to production-ready state in the shortest time, while maintaining iteration speed afterward.
When to use
Use this workflow when the user wants an end-to-end chain like:
- “ship this MVP”, “make it production-ready”, “launch/deploy this project”
- “take this prototype and turn it into a real app”
- “set up the foundation + UI system + deployment”
Core principles (non-negotiable)
- Pass paths only, not content: agents/sub-agents only pass
..._path. - Files are first-class citizens: Every step must persist artifacts; failures can be retried; replayable.
- Confirmation points: Any "high-risk/high-effort/side-effect" action must write a plan first and wait for confirmation.
- Plans are checklists: progress is tracked in
tasks.mdvia- [ ]→- [x](not in chat). - Progressive disclosure: Only open step files in this skill directory (
foundation.md,deploy-vercel.md, etc.) when needed—avoid loading all details at once. - Hooks doctor (required check; non-blocking): If running under Claude Code and you want the evolution loop active, run
tool-hooks-doctoronce at the start of the session; if hooks are missing, offer to install project-level hooks (continue either way).
Inputs / outputs (paths only)
Inputs (paths only):
repo_root: project root (default".")- Optional:
run_dir(active run directory) if the user already has one
Outputs (artifacts, written under run_dir/):
- Required:
proposal.md,tasks.md,context.json - Optional:
design.md,evidence/,logs/
Canonical contract (backends, templates, read order, auto-archive):
- references/artifact-contract.md
- Reference index: references/README.md
Step modules (open only when you hit that step)
- Foundation: foundation.md
- Guardrails: guardrails.md
- Trace cleanup: cleanup-traces.md
- Docs baseline: docs-baseline.md
- Supabase integration: supabase-integration.md
- Stripe integration: stripe-integration.md
- Deploy (GitHub + Vercel): deploy-vercel.md
- AI-era SEO (Next.js): ai-seo-nextjs.md
What ships with it
11 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.
- ai-seo-nextjs.md 1.7 KB
- cleanup-traces.md 3.5 KB
- deploy-vercel.md 1.2 KB
- docs-baseline.md 1019 B
- foundation.md 4.7 KB
- guardrails.md 1.9 KB
- references/artifact-contract.md 5.3 KB
- references/README.md 807 B
- scripts/auto_archive.py 6.4 KB runs code
- stripe-integration.md 1.8 KB
- supabase-integration.md 2.0 KB
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.
- 11d ago First seen · 241 lines · 109 tokens per session scan A d0a6a58d0e0c
workflow-ship-faster is a skill published in the GitHub repository Heyvhuang/ship-faster (339 stars, last pushed 26d ago), licensed MIT. It adds 109 tokens to every session and 3,145 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
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
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…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
menu-transitions-rtl
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…