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/willvelida/code-minions/creating-agent-skillnpx skills add willvelida/code-minions --skill creating-agent-skillgit clone --depth 1 https://github.com/willvelida/code-minionsWhat 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.00077 | $0.00757 |
| Opus 5 | $0.00039 | $0.00378 |
| Sonnet 5 | $0.00015 | $0.00151 |
| Haiku 4.5 | $0.00008 | $0.00076 |
Grade A, and why
creating-agent-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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Agent Skills
Overview
This skill provides capabilities for creating and reviewing Agent Skills that comply with the Agent Skills specification and follow authoring best practices.
Agent Skills are a lightweight, open format for extending AI agent capabilities with specialized knowledge and workflows. A skill is a folder containing a SKILL.md file with metadata and instructions, optionally bundled with scripts, references, and assets.
Capabilities
| Capability | Action | Description |
|---|---|---|
| Create | actions/create.md |
Generate a new, specification-compliant Agent Skill |
| Review | actions/review.md |
Analyse an existing skill for compliance and improvements |
Standards
This skill bundles the following standards in standards/:
| Standard | File | Description |
|---|---|---|
| Specification | specification.md |
Core Agent Skills format specification |
| Naming | naming.md |
Naming conventions for skills and files |
| Descriptions | descriptions.md |
Writing effective skill descriptions |
| Structure | structure.md |
Directory structure and progressive disclosure |
| Instructions | instructions.md |
Writing effective skill instructions |
| Clarifying Questions | clarifying-questions.md |
Questioning framework for gathering skill requirements |
| Checklist | checklist.md |
Consolidated compliance and quality checklist |
Principles
1. Concise is Key
The context window is a shared resource. Only add context the agent doesn't already have. Challenge each piece of information: "Does the agent really need this explanation?"
2. Progressive Disclosure
Structure skills for efficient context use:
- Metadata (~100 tokens):
nameanddescriptionloaded at startup - Instructions (<5000 tokens recommended): Full
SKILL.mdbody loaded when activated - Resources (as needed): Additional files loaded only when required
What ships with it
9 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.
- 3d ago First seen · 75 lines · 77 tokens per session scan A 103bfc56c52b
creating-agent-skill is a skill published in the GitHub repository willvelida/code-minions (23 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 77 tokens to every session and 757 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…