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 ragnar-pwninskjold/tech-snacks --skill scaffold-claudegit clone --depth 1 https://github.com/ragnar-pwninskjold/tech-snacksWrote 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/ragnar-pwninskjold/tech-snacks/scaffold-claude)<a href="https://agentmods.dev/skills/ragnar-pwninskjold/tech-snacks/scaffold-claude"><img src="https://agentmods.dev/badge/skills/ragnar-pwninskjold/tech-snacks/scaffold-claude/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/ragnar-pwninskjold/tech-snacks/scaffold-claude"><img src="https://agentmods.dev/badge/skills/ragnar-pwninskjold/tech-snacks/scaffold-claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Prompt Injection · line 16 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00099 | $0.01690 |
| Opus 5 | $0.00049 | $0.00845 |
| Sonnet 5 | $0.00020 | $0.00338 |
| Haiku 4.5 | $0.00010 | $0.00169 |
Grade A, and why
scaffold-claude 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
scaffold-claude
Scaffold a CLAUDE.md for the user's project. Output is written to a scratchpad so the user can review and move it to the repo root themselves.
The file you produce documents edge cases, non-obvious choices, and tribal knowledge — things Claude can't read off package.json, the directory tree, or the README. If a fact is derivable, it does not belong in the file.
The Iron Rule
Never write a section based on inference. Always ask, and stub when the answer is "skip" or "I don't know."
A stubbed section (a <!-- TODO: ... --> comment) is strictly better than a section filled with plausible-sounding guesses. Guesses encode false confidence that future Claude will trust.
When to Use
- User says
/scaffold-claudeor asks to "scaffold/write/create CLAUDE.md" - User asks for an AGENTS.md (same shape, different filename — ask which)
- User has a project but no CLAUDE.md and wants one
- User has a CLAUDE.md they want to redo from scratch
When NOT to Use
- User wants to edit an existing CLAUDE.md surgically → just edit it, don't run the full interview
- User wants a tiered, full-codebase AGENTS.md across many directories → use the
intent-layer-captureskill instead - User wants project-level CLAUDE.md updates triggered by code changes → that's a hook, not this skill
Output Location
Write to: docs/scratchpad/CLAUDE.md (relative to the user's current working directory)
- Confirm the path with the user before writing.
- If
docs/scratchpad/doesn't exist, create it. - If a file already exists at that path, ask before overwriting.
- Do NOT write to the repo root. The user moves the file when they're satisfied.
The Workflow
1. Scan (read-only, narrow)
Read these if they exist, only to identify what to ask about — not to fill in:
package.json,Gemfile,pyproject.toml,go.mod,Cargo.toml(any one that's present)- Top-level directory listing (just names, not contents)
README.md(skim, do not summarize into the CLAUDE.md)- Existing
CLAUDE.md,AGENTS.md,.cursorrules,.github/copilot-instructions.md— if any exist, mention them and ask whether to merge or start fresh
What ships with it
3 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.
- 12d ago First seen · 133 lines · 99 tokens per session scan A 883b4cc37c56
scaffold-claude is a skill published in the GitHub repository ragnar-pwninskjold/tech-snacks (132 stars, last pushed 25d ago), licensed MIT. It adds 99 tokens to every session and 1,690 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
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…
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…