Borrowing it
Nothing to install: this file belongs to snyk-labs/snyk-vulnbench. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/snyk-labs/snyk-vulnbench/main/.agents/skills/skill-creator-extra/SKILL.mdgit clone --depth 1 https://github.com/snyk-labs/snyk-vulnbenchWrote 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/snyk-labs/snyk-vulnbench/skill-creator-extra)<a href="https://agentmods.dev/skills/snyk-labs/snyk-vulnbench/skill-creator-extra"><img src="https://agentmods.dev/badge/skills/snyk-labs/snyk-vulnbench/skill-creator-extra/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/snyk-labs/snyk-vulnbench/skill-creator-extra"><img src="https://agentmods.dev/badge/skills/snyk-labs/snyk-vulnbench/skill-creator-extra.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.00126 | $0.03691 |
| Opus 5.5 | $0.00050 | $0.01476 |
| Sonnet 5.5 | $0.00025 | $0.00738 |
| Haiku 4.5 | $0.00013 | $0.00369 |
Grade A, and why
skill-creator-extra 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 1mo 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 — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator Extra
Instructions
A great skill is not just documentation — it's a set of instructions that drives an agent to a concrete outcome without requiring the user to direct every step. This skill layers structured enhancement phases on top of the official Claude skill creator to produce skills that are well-designed, properly structured, and immediately useful.
The official skill creator plugin handles the core loop of draft → test → evaluate → improve. These phases pick up where it leaves off, adding the craft that turns a functional skill into an excellent one.
Before starting, identify which kind of skill you're building:
- Capability skills help the agent do something the base model can't do consistently on its own (e.g., filling PDF forms, calling a niche API). These may become unnecessary as models improve — evals will tell you when.
- Preference skills encode a specific workflow or team convention (e.g., your code review steps, your deploy process). These are durable but need to stay in sync with your actual process.
Phase 1: Start with the official skill creator
Begin every new skill by running the official Claude skill creator plugin: https://claude.com/plugins/skill-creator
It handles:
- Capturing intent and interviewing the user
- Drafting the initial SKILL.md
- Writing test cases and running evals
- Iterating based on qualitative and quantitative feedback
- Optimizing the description for triggering accuracy
- Packaging the final skill
Complete this phase fully before moving to the enhancement phases below. The enhancements are most useful once a working draft exists.
Phase 2: Design around concrete use-cases
Review the draft skill for 2–3 concrete use-cases. Each use-case must answer three questions:
- What is the goal? — the outcome the user wants, stated plainly
- What are the steps? — numbered, specific, executable
- When is it done? — a clear completion condition that Claude can verify
What ships with it
1 file 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.
- 1mo ago First seen · 387 lines · 126 tokens per session scan A 4fdde9f1fade
skill-creator-extra is a skill published in the GitHub repository snyk-labs/snyk-vulnbench (4 stars, last pushed 14d ago), licensed Apache-2.0. It adds 126 tokens to every session and 3,691 once invoked, about $0.0005 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…