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/drn/dots/releasenpx skills add drn/dots --skill releasegit clone --depth 1 https://github.com/drn/dotsWhat 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.00034 | $0.00996 |
| Opus 5 | $0.00017 | $0.00498 |
| Sonnet 5 | $0.00007 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
release 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Create a versioned release: bump version, generate changelog, create git tag, and publish a GitHub release.
Arguments
$ARGUMENTS- Required: version bump type (major,minor,patch) or an explicit version (e.g.,v2.1.0). Optional:--dry-runto preview without creating anything.
Context
- Current branch: !
git branch --show-current - Git status: !
git status --short - Latest tag: !
git describe --tags --abbrev=0 2>/dev/null | head -1 - Commits since last tag: !
git log --oneline 2>/dev/null | head -30 - Remotes: !
git remote -v 2>/dev/null | head -10 - Base ref: !
git branch -r 2>/dev/null | grep -oE 'origin/(main|master)' | head -1
Instructions
Step 0: Validate state
- IF
git status --shortshows uncommitted changes, stop: "Uncommitted changes detected. Commit or stash before releasing." - Determine the default branch using
git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null. Fallback to checking fororigin/main, thenorigin/master. - IF the current branch is not the default branch and does not match
release/*, warn: "You are on , not the default branch. Releases are typically made from . Proceed anyway?" Wait for confirmation.
Step 1: Determine version
Parse $ARGUMENTS for the version:
- IF an explicit version is given (e.g.,
v2.1.0), use it directly. - IF a bump type is given (
major,minor,patch):- Parse the latest tag from context. IF no tags exist, start from
v0.0.0. - Apply the bump. Examples:
v1.2.3+ patch =v1.2.4, + minor =v1.3.0, + major =v2.0.0. - Preserve the tag prefix (if existing tags use
v, keepv; if bare numbers, use bare numbers).
- Parse the latest tag from context. IF no tags exist, start from
Report: "Version: -> "
Step 2: Generate changelog
Fetch commits since the last tag (or all commits if no prior tag):
git log <last-tag>..HEAD --format="%H%n%s%n%b%n---END---"
Categorize using the same approach as /changelog:
- Added — new features, commands, capabilities
- Changed — modifications to existing behavior
- Fixed — bug fixes
- Removed — deleted features, deprecated code
- Infrastructure — CI/CD, build, dependencies
- Documentation — docs, README
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 · 115 lines · 34 tokens per session scan A 2280e880e3c5
release is a skill published in the GitHub repository drn/dots (23 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 996 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…