skill-creator

skill-creator is a skill for Claude Code, Codex from HazAT/pi-config. It costs 67 tokens per session (2,533 once invoked), scanned B, original, MIT.

A guide for creating new agent skills, which are reusable instructions that tell a coding agent how to handle a particular kind of task.

In plain words
What is it for?
Use it to plan, write, register, and verify a new skill stored in a SKILL.md file.
Why use it?
It helps turn a rough idea into a skill with a clear purpose, trigger conditions, structure, and checks. It also helps avoid naming conflicts and incomplete setup.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

Install

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.

agentmods
npx agentmods add skills/hazat/pi-config/skill-creator
Any agent
npx skills add HazAT/pi-config --skill skill-creator
Clone the repo
git clone --depth 1 https://github.com/HazAT/pi-config

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for skill-creator

README.md
[![agentmods](https://agentmods.dev/badge/skills/hazat/pi-config/skill-creator.svg)](https://agentmods.dev/skills/hazat/pi-config/skill-creator)
Your own site
<a href="https://agentmods.dev/skills/hazat/pi-config/skill-creator"><img src="https://agentmods.dev/badge/skills/hazat/pi-config/skill-creator.svg" alt="Measured on agentmods" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,533 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00067 $0.02533
Opus 5 $0.00034 $0.01267
Sonnet 5 $0.00013 $0.00507
Haiku 4.5 $0.00007 $0.00253

Measured 6d ago against content hash 93b543a0514f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade B, and why

skill-creator scanned grade B with 1 finding 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 6d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/quick_validate.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Unrestricted tool accessmediumExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

- `allowed-tools` — comma-separated list (e.g., `Read, Grep, Glob, Bash`); omit to allow all tools
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/skill-creator/SKILL.md · 285 lines

How it starts

The opening of the file, as written. The whole thing — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create a New Skill

Guide the user through creating a new agent skill following the Agent Skills specification. Follow each step in order.

Step 1: Understand the Skill

Gather requirements before writing anything.

Ask the user:

  1. What should this skill do? (one sentence)
  2. When should an agent use it? (trigger phrases users would say)
  3. What tools does the skill need? (Read, Grep, Glob, Bash, Task, WebFetch, etc.)
  4. Where should the skill live? (which plugin or directory)

Determine the skill name:

  • Lowercase letters, digits, and hyphens only (a-z, 0-9, -)
  • 1-64 characters; must not start or end with -; no consecutive hyphens (--)
  • Descriptive and unique among existing skills
  • Prefer action-oriented names: processing-pdfs, fix-issue, code-review
  • Check the target skills directory to avoid name collisions

Choose a complexity tier:

Tier Structure Use When
Simple SKILL.md only Self-contained instructions under ~200 lines
With references SKILL.md + references/ Domain knowledge that agents load conditionally
With scripts SKILL.md + scripts/ Workflow automation needing Python scripts
Full All of the above Complex skills with automation and domain knowledge

Read ${CLAUDE_SKILL_ROOT}/references/design-principles.md for guidance on keeping skills focused and concise.

Step 2: Plan the Skill

Analyze how each use case would be executed from scratch. Identify what reusable resources would help when executing these tasks repeatedly.

For each concrete example, ask:

  1. What code would be rewritten every time? → candidate for scripts/
  2. What documentation is needed to inform decisions? → candidate for references/
  3. What templates or assets are used in output? → candidate for assets/

Example analysis:

  • "Rotate a PDF" → rotating requires rewriting the same code → scripts/rotate_pdf.py
  • "Query BigQuery metrics" → need table schemas each time → references/schema.md
  • "Build a frontend app" → same boilerplate HTML/React → assets/hello-world/

Read the full file on GitHub · 285 lines

Files

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.

Changes

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.

  1. 6d ago First seen · 285 lines · 67 tokens per session scan B 93b543a0514f

Subscribe to this mod's changes

skill-creator is a skill published in the GitHub repository HazAT/pi-config (443 stars, last pushed 12d ago), licensed MIT. It adds 67 tokens to every session and 2,533 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens