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 skills add drn/dots --skill write-skillgit clone --depth 1 https://github.com/drn/dotsWrote 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/drn/dots/write-skill)<a href="https://agentmods.dev/skills/drn/dots/write-skill"><img src="https://agentmods.dev/badge/skills/drn/dots/write-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.1 | $0.00042 | $0.02840 |
| Opus 5 | $0.00021 | $0.01420 |
| Sonnet 5 | $0.00008 | $0.00568 |
| Haiku 4.5 | $0.00004 | $0.00284 |
Grade A, and why
write-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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Author
Create or improve Claude Code skills (slash commands) following established patterns and avoiding known pitfalls.
Arguments
$ARGUMENTS- What the skill should do, or the name of an existing skill to improve
Context
- Global skills: !
find ~/.claude/commands -maxdepth 1 -name "*.md" -exec basename {} .md \; 2>/dev/null | sort | head -20 - Project skills (Agent Skills standard): !
find . -maxdepth 3 -path "*/skills/*/SKILL.md" 2>/dev/null | head -20 - Project skills (Claude Code standard): !
find . -path "./claude/commands/*.md" 2>/dev/null | head -20 - Project type: !
find . -maxdepth 1 \( -name go.mod -o -name Gemfile -o -name package.json -o -name Cargo.toml -o -name pyproject.toml \) 2>/dev/null | head -3
Instructions
Step 1: Understand the Request
Determine whether the user wants to:
- Create a new skill from a description
- Improve an existing skill (read it first, then apply changes)
If creating, ask the user what the skill should do if $ARGUMENTS is vague.
Step 2: Design the Skill
Plan the skill structure:
- Frontmatter (YAML between
---fences) - Context section (dynamic context via shell commands)
- Instructions (what Claude should do when the skill is invoked)
Step 3: Write the Skill File
Detect the project skill convention from the context above:
- If the project has skills matching
*/skills/*/SKILL.md(Agent Skills standard), create<skills-dir>/<name>/SKILL.md - Otherwise, create
claude/commands/<name>.md(Claude Code standard)
Follow all rules below carefully.
Skill File Reference
Frontmatter
All fields are optional. Only description is strongly recommended.
---
description: One-line summary of what this skill does and when to use it
allowed-tools: Bash(git *), Bash(npm test)
---
| Field | Purpose |
|---|---|
description |
Drives auto-activation and / menu. Write in third person. Max 1024 chars. Include trigger keywords. |
allowed-tools |
Tools Claude can use without asking permission. Glob patterns supported. |
context |
Set to fork to run in an isolated subagent (no conversation history). |
agent |
Subagent type when context: fork (e.g., Explore, Plan). |
model |
Override model (e.g., sonnet for cheaper tasks). |
disable-model-invocation |
true to prevent auto-loading (manual /name only). Use for destructive skills. |
user-invocable |
false to hide from / menu (background knowledge only). |
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 · 243 lines · 42 tokens per session scan A f749764b377a
write-skill is a skill published in the GitHub repository drn/dots (23 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 2,840 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…