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 AlteredCraft/claude-code-plugins --skill create-skillgit clone --depth 1 https://github.com/AlteredCraft/claude-code-pluginsWrote 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/alteredcraft/claude-code-plugins/create-skill)<a href="https://agentmods.dev/skills/alteredcraft/claude-code-plugins/create-skill"><img src="https://agentmods.dev/badge/skills/alteredcraft/claude-code-plugins/create-skill/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/alteredcraft/claude-code-plugins/create-skill"><img src="https://agentmods.dev/badge/skills/alteredcraft/claude-code-plugins/create-skill.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.00201 | $0.04510 |
| Opus 5.5 | $0.00080 | $0.01804 |
| Sonnet 5.5 | $0.00040 | $0.00902 |
| Haiku 4.5 | $0.00020 | $0.00451 |
Grade A, and why
create-skill 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 2mo 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Anchored Interview Skill Creator
Interview the user to produce a new Claude Code skill that follows the Anchored Interview pattern: grounded in a CORPUS, run an interview sharpened by that grounding, then produce a single ARTIFACT. The output is a complete skill directory (SKILL.md + references/<artifact>-template.md, optional scripts) the user can drop into their project, user-global skills, or a plugin.
Why this skill exists
The Anchored Interview is a recurring shape: skills that ground in something concrete (a codebase, a notes folder, a docs site, a transcript archive) and then run a short, adaptive interview whose questions reference what was found in the grounding. The questions get sharper because something concrete preceded them. Done well, the pattern recovers a lot of the value lost to vague or generic skill interviews.
This meta-skill is itself an instance of that pattern — its CORPUS is two bundled worked-example skills (one code-corpus, one docs-corpus) plus a parameterized blueprint; its ARTIFACT is a new skill directory. The recursion is intentional. The most reliable way to teach someone (human or model) to produce something is to walk them through producing it, anchored in real exemplars.
The pattern's invariant: ground before you interview; interview before you act. Anything that breaks that invariant doesn't belong in this skill's output.
Workflow
The sequence matters. Do not jump ahead.
1. Confirm the seed intent in one sentence
Before reading any source material, get the user's intent in one sentence: what type of Anchored Interview skill do you want to create?
If they already said it clearly in the prompt, paraphrase it back and ask "is that right?" — don't make them repeat themselves. If their seed is vague ("I want a skill for my writing"), ask one or more clarifying questions to narrow it before grounding. Grounding the wrong area is wasted work. DO NOT go too deep at this point — just enough to shape the grounding step.
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.
- 2mo ago First seen · 161 lines · 0 tokens per session scan A 1e0816e0ff0b
create-skill is a skill published in the GitHub repository AlteredCraft/claude-code-plugins (12 stars, last pushed 5mo ago), licensed MIT. It adds 201 tokens to every session and 4,510 once invoked, about $0.0008 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-30.
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…