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/clivechung/skillmcp/write-a-skillnpx skills add clivechung/skillmcp --skill write-a-skillgit clone --depth 1 https://github.com/clivechung/skillmcpWrote 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/clivechung/skillmcp/write-a-skill)<a href="https://agentmods.dev/skills/clivechung/skillmcp/write-a-skill"><img src="https://agentmods.dev/badge/skills/clivechung/skillmcp/write-a-skill.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.00048 | $0.01231 |
| Opus 5 | $0.00024 | $0.00616 |
| Sonnet 5 | $0.00010 | $0.00246 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
write-a-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 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write A Skill
Guide the user through creating robust, predictable, and token-efficient AI agent skills using Matt Pocock's skill authoring methodology and the standard SKILL.md format.
The 4-Phase Authoring Workflow
Follow these four phases sequentially when authoring or refining a skill:
┌────────────────────────┐
│ 1. Gather Requirements│ ──► Identify domain, use cases, triggers & scripts
└───────────┬────────────┘
│
▼
┌────────────────────────┐
│ 2. Draft the Skill │ ──► Structure SKILL.md, references/, examples/, scripts/
└───────────┬────────────┘
│
▼
┌────────────────────────┐
│ 3. Review & Validate │ ──► Check triggers, edge cases & progressive disclosure
└───────────┬────────────┘
│
▼
┌────────────────────────┐
│ 4. Finalize │ ──► Place in skills/<name>/, link references, test syntax
└────────────────────────┘
Phase 1: Gather Requirements
Before writing any markdown, interview the user to clarify:
- Skill Name & Category: What specific problem or capability does this skill address? What category does it belong to (e.g.,
software,for-fun, or a new domain category)? (Lowercase, hyphenated, matching folder name). - Trigger Criteria: When should the agent reach for this skill? What user prompts, keywords, or workflows should trigger it?
- Execution Model:
- Deterministic Steps: Can repetitive, fragile, or complex commands be encapsulated into scripts (in
scripts/)? - Procedural Steps: What sequence of actions, decisions, and checks must the agent follow?
- Deterministic Steps: Can repetitive, fragile, or complex commands be encapsulated into scripts (in
- Reference Material & Depth:
- Is there bulky documentation, API specs, or cheatsheets that should be moved into
references/rather than clutteringSKILL.md? - Are there concrete input/output examples that belong in
examples/?
- Is there bulky documentation, API specs, or cheatsheets that should be moved into
Phase 2: Draft the Skill
Create the skill directory under skills/<category>/<skill-name>/ (or .agents/skills/<skill-name>/ for workspace meta-skills) with the following structure:
What ships with it
3 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 · 141 lines · 48 tokens per session scan A 044552b3cb2c
write-a-skill is a skill published in the GitHub repository clivechung/skillmcp (0 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 1,231 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
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…