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 agentmods add skills/anilcancakir/claude-code-plugin/skill-creatornpx skills add anilcancakir/claude-code-plugin --skill skill-creatorgit clone --depth 1 https://github.com/anilcancakir/claude-code-pluginWrote 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/anilcancakir/claude-code-plugin/skill-creator)<a href="https://agentmods.dev/skills/anilcancakir/claude-code-plugin/skill-creator"><img src="https://agentmods.dev/badge/skills/anilcancakir/claude-code-plugin/skill-creator.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.01453 |
| Opus 5 | $0.00016 | $0.00727 |
| Sonnet 5 | $0.00007 | $0.00291 |
| Haiku 4.5 | $0.00003 | $0.00145 |
Grade A, and why
skill-creator 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 3d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator
Create high-quality Claude Code skills following progressive disclosure — metadata always loaded, SKILL.md body on trigger, references on demand.
Core Process
1. Interview
Gather requirements through focused questions. Limit to 3-4 AskUserQuestion calls maximum:
- What should this skill enable?
- When should it trigger? (user phrases, file patterns, contexts)
- What tools does it need? (Read, Write, Edit, Bash, Agent, etc.)
- Where should it run? (Skills loaded into the main session inherit the user's chosen model. Only specify a model when the skill ships an agent with its own override.)
Skip questions where the answer is obvious from context.
2. Explore Existing Patterns
Use Glob + Read directly to find existing conventions in the target project:
- Glob
**/skills/**/SKILL.mdto list defined skills, read 2-3 closest matches - Sample the file structure and naming conventions via
ls - Detect the technology stack from manifest files (
package.json,composer.json,pubspec.yaml)
3. Dedup Audit
Read ${CLAUDE_SKILL_DIR}/../prompt-writer/references/cc-dedup-guide.md before drafting. Check what CC already provides natively — the skill body must not repeat general concepts the model already knows. Cut anything CC handles by default.
4. Draft Skill
Follow progressive disclosure. SKILL.md body ≤500 lines. Move detail to references/. Read references/skill-patterns.md for description patterns, invocation control, string substitutions, and directory structure before writing.
Key decisions at this stage:
- Which description pattern fits? (A/B/C/D — see skill-patterns.md)
user-invocable: false?disable-model-invocation: true? (see Invocation Control Matrix)context: forkif the skill is self-contained and parallelizable?paths:if the skill activates only for specific file types?
5. Wire References
CC does NOT auto-load references/ files. The model never sees them unless SKILL.md points to them explicitly.
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.
- 3d ago First seen · 136 lines · 33 tokens per session scan A d54bed2cf1dd
skill-creator is a skill published in the GitHub repository anilcancakir/claude-code-plugin (2 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 1,453 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-31.
Other skills, from other repositories
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
verify-dotnet-samples
How to build, run and verify the .NET sample projects in the Agent Framework repository. Use this when a user wants to verify that the samples still function as expected.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.