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 ScottDuncanAI/claude-manufacturing-skills --skill skill-templategit clone --depth 1 https://github.com/ScottDuncanAI/claude-manufacturing-skillsWrote 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/scottduncanai/claude-manufacturing-skills/skill-template)<a href="https://agentmods.dev/skills/scottduncanai/claude-manufacturing-skills/skill-template"><img src="https://agentmods.dev/badge/skills/scottduncanai/claude-manufacturing-skills/skill-template/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/scottduncanai/claude-manufacturing-skills/skill-template"><img src="https://agentmods.dev/badge/skills/scottduncanai/claude-manufacturing-skills/skill-template.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.00048 | $0.00452 |
| Opus 5 | $0.00024 | $0.00226 |
| Sonnet 5 | $0.00010 | $0.00090 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
skill-name-in-kebab-case 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 12d 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.
What it actually says
Skill Name
One or two sentences on what a good result looks like and who judges it. Naming the reviewer — "a process engineer who will spot a backwards arrowhead" — sets the bar far better than an adjective like "high quality".
Non-negotiable output rules
The handful of things that make the output wrong if violated. Keep this short; if everything is non-negotiable, nothing is.
- …
- …
Workflow
1. Read the request and fill the gaps
What is almost always underspecified? List the questions worth asking, and cap them (e.g. "ask at most 2–3, and only for things that change the answer"). For everything else, make a defensible assumption and state it afterward.
2. Plan before producing
The step that prevents rework.
3. Produce
Point at scripts/ and references/ here rather than restating their contents:
scripts/<module>.pyprovides the primitives. Read it before writing anything and use it rather than reinventing. Readreferences/<topic>.mdfor the conventions.
4. Check the output and fix it
The step that separates a passable result from a professional one. Render it, run it, or validate it — then actually look at the result and iterate. Say how many rounds to expect and list the defects that are only visible on inspection.
5. Deliver
Where the output goes, and what to state alongside it: assumptions made, anything that couldn't be done and why, and any concern noticed along the way. Flagging concerns is usually a large part of the value.
What this skill does not do
State the limits plainly, and say so to the user if their framing suggests they expect more. Everything in this repo is conceptual, engineering-support output — not issued-for-design work, not hazard analysis, not equipment sizing.
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.
- 12d ago First seen · 44 lines · 48 tokens per session scan A 34dee439303f
skill-name-in-kebab-case is a skill published in the GitHub repository ScottDuncanAI/claude-manufacturing-skills (51 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 452 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…
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…