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/helderberto/agent-skills/create-skillnpx skills add helderberto/agent-skills --skill create-skillgit clone --depth 1 https://github.com/helderberto/agent-skillsWhat 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.00073 | $0.02657 |
| Opus 5 | $0.00036 | $0.01328 |
| Sonnet 5 | $0.00015 | $0.00531 |
| Haiku 4.5 | $0.00007 | $0.00266 |
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 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Skills
Process
- Gather requirements — ask the user (use AskUserQuestion when available; otherwise present numbered options):
- What task or domain does the skill cover?
- What specific use cases should it handle?
- Does it need executable scripts, or just instructions?
- Any reference material to include?
- Explore existing skills —
ls skills/and read 1–2 neighbors to match conventions. - Draft — create
SKILL.md; split deep material intoreferences/if it exceeds ~150 lines; addscripts/only for deterministic helpers. - Review with user — present the draft and ask:
- Does this cover your use cases?
- Anything missing or unclear?
- Should any section be more or less detailed?
Skill Structure
skill-name/
├── SKILL.md # Required. Metadata + instructions.
├── references/ # Optional. Long-form docs the agent reads on demand.
│ └── <topic>.md
├── scripts/ # Optional. Deterministic helpers (.sh, .py) called via Bash.
│ └── helper.sh
└── assets/ # Optional. Files used in output (templates, icons, fonts).
└── template.md
Keep the entry point in SKILL.md. Link from SKILL.md to references/<topic>.md rather than inlining — preserves progressive disclosure.
Progressive disclosure (three levels)
- Metadata (
name+description) — always in context (~100 words). Sole signal for triggering. SKILL.mdbody — loaded when skill triggers. Keep under ~150 lines; the spec ceiling is ~500.- Bundled resources (
references/,scripts/,assets/) — loaded on demand or executed without loading.
SKILL.md Template
---
name: skill-name
description: One sentence what it does. Use when [triggers]. Don't use when [anti-triggers].
---
# Skill Name
[body — steps, reference, or both]
A skill's body is built from two content types that mix freely: steps (ordered actions the agent takes) and reference (definitions, rules, facts consulted on demand). A skill can be all steps, all reference, or both — let the content pick the shape. Don't force Workflow / Rules / Error Handling headings onto a skill that doesn't need them; empty scaffolding sections are no-ops (see Failure Modes).
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 · 194 lines · 73 tokens per session scan A 3bd5d7c8a6e6
create-skill is a skill published in the GitHub repository helderberto/agent-skills (13 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 2,657 once invoked, about $0.0004 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-30.
Other skills, from other repositories
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
batch-simplify
Batch-run simplification across changed files, or across an entire repository, grouped by ecosystem and dependency order. Use when: 'batch simplify', 'simplify recent changes', 'simplify everything', 'forgot to run simplify', 'catch up on simplify', 'simplify my branch changes', 'simplify the whole repo', 'simplify…
audit-install-state
Read-only audit of a Claude Code INSTALLATION directory, the machine-scope /.claude tree plus /.claude.json. Inventorying every file, separating what the product's own retention sweep already manages from what nothing manages, resolving what each number in a filename actually means before any process-liveness check…
audit-native-overlap
Map native Claude Code surfaces, built-in CLI commands, bundled skills, plugin-backed built-ins, session-provided skills, against the current repo's plugin skills and agents, so a custom component never silently duplicates what Claude Code itself now ships. Bare invocation is a READ-ONLY report: overlap candidates…
gerador-soul
Gera um arquivo SOUL.md completo e estruturado para qualquer agente ou assistente de IA. Use esta skill SEMPRE que a pessoa usuária quiser criar um SOUL.md, definir a identidade de um agente, descrever a "alma" de um assistente, ou usar os gatilhos "/soul", "/soul.md" ou "gerar soul". Ative também quando a pessoa…