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/skillscatalog/registry/skill-createnpx skills add SkillsCatalog/registry --skill skill-creategit clone --depth 1 https://github.com/SkillsCatalog/registryWhat 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.00028 | $0.00675 |
| Opus 5 | $0.00014 | $0.00338 |
| Sonnet 5 | $0.00006 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
skill-create 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 2d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
Use this skill to create new Agent Skills from templates. It generates a properly structured skill directory with a valid SKILL.md file and optional scripts/assets folders.
When to Use
- Starting a new skill from scratch
- Ensuring proper skill structure and naming
- Quickly prototyping new skill ideas
- Teaching others how to structure skills
How to Use
Create a new skill with a name:
Create a new skill called "pdf-tools"
Create a skill with a specific template:
Create a new skill called "data-analyzer" using the with-scripts template
Available templates:
- basic - Just SKILL.md (default)
- with-scripts - SKILL.md + scripts directory
- with-assets - SKILL.md + scripts + assets directories
Output
Creates a complete skill directory:
Basic template:
pdf-tools/
├── SKILL.md
└── README.md
With-scripts template:
pdf-tools/
├── SKILL.md
├── README.md
└── scripts/
└── main.py
With-assets template:
pdf-tools/
├── SKILL.md
├── README.md
├── scripts/
│ └── main.py
└── assets/
└── .gitkeep
Examples
Basic skill:
User: Create a new skill called "code-formatter"
Agent: Creating skill "code-formatter" with basic template...
Created:
✓ code-formatter/SKILL.md
✓ code-formatter/README.md
Next steps:
1. Edit SKILL.md with your skill's instructions
2. Add any supporting files
3. Run skill-validator to check compliance
Interactive mode:
User: Create a new skill
Agent: I'll help you create a new skill.
Skill name: code-formatter
Description: Format code in various languages
Template: with-scripts
License: MIT
Creating...
✓ Created code-formatter with with-scripts template
With metadata:
User: Create a new skill called "api-tester" with description "Test REST APIs" and author "acme-corp"
Agent: Creating skill "api-tester"...
✓ Created with custom metadata:
- Description: Test REST APIs
- Author: acme-corp
- License: MIT (default)
What ships with it
2 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.
- 2d ago First seen · 127 lines · 28 tokens per session scan A 83d1f4803d5b
skill-create is a skill published in the GitHub repository SkillsCatalog/registry (1 stars, last pushed 8mo ago), licensed MIT. It adds 28 tokens to every session and 675 once invoked, about $0.0001 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-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
Developmental Gene Panel Design Workflow
Panel design for DEVELOPING / dynamic systems (embryonic organs, differentiation, regeneration). The target experiment is usually a LATE / terminal stage, but the biology is a trajectory: terminal cell types are end-products of earlier lineage programs. A panel built from the target stage alone resolves terminal…
accessibility-audit
Run a comprehensive WCAG accessibility audit covering perceivable, operable, understandable, and robust principles. Use this skill whenever the user wants to audit accessibility, review WCAG compliance, fix accessibility issues, prepare for accessibility certification, address an accessibility lawsuit risk, or…
to-issues
Decompose a PRD and/or SPEC into implementable, vertically-sliced Issues with real blocking edges, then create them in your chosen platform (GitHub or Local). Use after /prd (and optionally /prd-to-spec) to turn requirements into agent-ready tickets. Triggers on: create issues, to-issues, 创建issue, 拆解issue, 生成卡片, 创建卡片…
trtllm-code-contribution
Best practices for contributing code to TensorRT-LLM. Covers the official contribution process (issue tracking, fork workflow, DCO signing), coding guidelines, implementation workflow, common mistakes, testing strategy, commit hygiene, and review readiness. Incorporates rules from CONTRIBUTING.md and…
checkup-simplify
Use this skill when the user asks for conservative cleanup of already changed source files, similar to Claude Code /simplify, but the active agent may be Cursor, Codex, Gemini, or OpenCode.