Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add raisedadead/claude-code-plugins/plugin install whetstoneWrote 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/raisedadead/claude-code-plugins/skill-smith)<a href="https://agentmods.dev/skills/raisedadead/claude-code-plugins/skill-smith"><img src="https://agentmods.dev/badge/skills/raisedadead/claude-code-plugins/skill-smith/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/raisedadead/claude-code-plugins/skill-smith"><img src="https://agentmods.dev/badge/skills/raisedadead/claude-code-plugins/skill-smith.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.00066 | $0.01274 |
| Opus 5.5 | $0.00026 | $0.00510 |
| Sonnet 5.5 | $0.00013 | $0.00255 |
| Haiku 4.5 | $0.00007 | $0.00127 |
Grade A, and why
skill-smith 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 2d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
skill-smith — lint a SKILL.md
A skill lives or dies on its routing and its shape. The script judges the deterministic half — frontmatter, line budget, reference depth — and hands you a checklist for the half it cannot.
When to use
- Authoring a new skill — run it before calling the skill done.
- Reviewing or editing an existing
SKILL.md. - After any edit under a
skills/*/SKILL.mdpath.
Run the lint
"${CLAUDE_PLUGIN_ROOT}"/bin/lint-skill <path-to-SKILL.md>
Pass a single SKILL.md, or a skills/ directory to lint every skill under it. Exit 1 when any FAIL is present; WARN alone exits 0.
What it checks, deterministically:
- name — present, matches the parent directory, and uses the kebab charset (lowercase / digits / single hyphens, no leading, trailing, or doubled hyphen).
- description — present, ≤ 1024 chars, carries a
Use when/Invoke whentrigger clause, and reads third-person (a first-personI …is flagged). - body — under the 500-line budget (a warning fires past 400).
- reference depth — every bundled file (
reference/…,scripts/…) stays one level deep; a file nested deeper is aWARN, so the run still exits 0 and the rule is yours to hold.
The loop
Fix the reported FAILs, re-run, repeat — cap at 3 rounds. Findings still standing after the third round go to the operator as a residual list. The exit criterion is lint-skill exiting 0, judged by the script.
WARNs exit 0 and are still worth reading — a first-person description or a body creeping toward the budget is cheapest to fix while you are here.
Manual pass (what the script cannot judge)
Three things stay judgement calls. Before you write, read reference/writing-for-agents.md; after the lint is clean, read the change against the other two:
reference/writing-for-agents.md— the rubric for any document an agent reads: context pointers, the information hierarchy, completion criteria, leading words and pruning. A skill also readsreference/skill-mechanics.md.reference/anatomy.md— the canonical section order and the frontmatter contract. Diff a new skill's shape against it.reference/failure-modes.md— the six ways a skill rots (premature completion, duplication, sediment, sprawl, no-op, negation). Use it as a read-through checklist.
What ships with it
6 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.
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.
- 2d ago Changed · +1 lines 31b7e240ebde
- 7d ago Changed 1f3e3c6a9bdc
- 14d ago Changed · +2 lines 67188a87a134
- 1mo ago First seen · 68 lines · 66 tokens per session scan A 8b86ec070f39
skill-smith is a skill published in the GitHub repository raisedadead/claude-code-plugins (3 stars, last pushed today), licensed ISC. It adds 66 tokens to every session and 1,274 once invoked, about $0.0003 per session on Opus 5.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-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…