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-template-seedergit 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-template-seeder)<a href="https://agentmods.dev/skills/heyvhuang/ship-faster/workflow-template-seeder"><img src="https://agentmods.dev/badge/skills/heyvhuang/ship-faster/workflow-template-seeder/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-template-seeder"><img src="https://agentmods.dev/badge/skills/heyvhuang/ship-faster/workflow-template-seeder.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 Excessive Agency · line 40 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00057 | $0.00668 |
| Opus 5 | $0.00028 | $0.00334 |
| Sonnet 5 | $0.00011 | $0.00134 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
workflow-template-seeder 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow: Template Seeder (Skills → Templates)
Goal: Turn a short template spec into a runnable, documented template under templates/.
This workflow is skills-first:
- Use skills as the primary execution engine
- Treat templates as “frozen outputs” (examples + regression references), not the mainline product
Input (pass paths only)
repo_root: Ship Faster repository root (wheretemplates/lives)run_dir:runs/template-seeder/active/<run_id>/template_spec.md: One-page spec (what it is, target user, core pages, required integrations)
Output (persisted)
03-plans/template-plan.md05-final/template-summary.md- A new template directory:
templates/<NNN>-<slug>/containing:README.md(5‑minute runnable).env.local.example(keys only)metadata.json
Workflow
0) Initialize
- Create
run_dir. - Determine:
<slug>from spec (kebab-case)<NNN>as the next available number undertemplates/(001, 002, …)
- Write
01-input/context.jsonfor this workflow:entry_type: idearepo_root: <path-to-new-template-dir>need_deploy: false(templates should not auto-deploy)- Enable only the integrations required by the spec (DB/billing/SEO)
1) Generate the template baseline (prefer clean + minimal)
Preferred path:
- Create a clean Next.js baseline in the new template directory, then run the same “Ship Faster chain” against it.
Execution order (recommended):
workflow-project-intake(optional if spec is already complete)workflow-ship-fasterwith the template directory asrepo_root- If any steps are skipped (e.g., no DB/billing), record why in
00-index.md/05-final/template-summary.md
2) Template hardening (shareable output)
Must do:
- Remove secrets; only keep env key names in
.env.local.example - Ensure
README.mdincludes:- Node version
- install + dev
- required env keys
- optional integrations notes
- Ensure
metadata.jsonis accurate and generic (no private branding unless intended)
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 · 76 lines · 57 tokens per session scan A 204e351c9d60
workflow-template-seeder is a skill published in the GitHub repository Heyvhuang/ship-faster (339 stars, last pushed 26d ago), licensed MIT. It adds 57 tokens to every session and 668 once invoked, about $0.0003 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…