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/guardnpx skills add drn/dots --skill guardgit 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.00035 | $0.00993 |
| Opus 5 | $0.00017 | $0.00496 |
| Sonnet 5 | $0.00007 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
guard scanned grade A with 1 finding 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- `chmod 777` or world-readable permissions Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-commit Guard
Fast safety check before committing. Scans for secrets, security antipatterns, test breakage, and lint issues. Binary pass/fail output.
Arguments
$ARGUMENTS- Optional:--strictfor zero-tolerance mode (warnings also fail)
Context
- Staged files: !
git diff --cached --name-only - Unstaged changes: !
git diff --name-only - 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
Run these checks against all staged files (or all changed files if nothing is staged). Be fast -- this is a pre-commit gate, not a full review.
Check 0: Gitignore Violations
Scan staged/changed files for common files that should not be committed:
.env,.env.*files (environment/secrets)node_modules/contents- Build artifacts (
dist/,build/,*.o,*.pyc,__pycache__/) - IDE files (
.idea/,.vscode/settings.json) - OS files (
.DS_Store,Thumbs.db) - Log files (
*.log) - Credential files (
credentials.json,*.pem,*.key)
Report: WARNING if any found (FAIL in --strict mode).
Check 1: Secrets Detection
Scan staged/changed files for:
- API keys, tokens, passwords (patterns:
password\s*=,api_key,secret,token\s*=,Bearer) - AWS credentials (
AKIA,aws_secret_access_key) - Private keys (
-----BEGIN.*PRIVATE KEY-----) - Connection strings with embedded credentials
.envfiles being committed- Hardcoded URLs with credentials (
https://user:pass@)
Report: FAIL if any found, with file and line number.
Check 2: Security Antipatterns
Scan for common dangerous patterns:
eval()orexec()with variable input- SQL string concatenation (instead of parameterized queries)
dangerouslySetInnerHTMLor equivalent- Disabled SSL verification (
verify: false,VERIFY_NONE) - Overly permissive CORS (
Access-Control-Allow-Origin: *) chmod 777or world-readable permissions--no-verifyor security bypass flags in code
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 · 121 lines · 35 tokens per session scan A b5257b4cd91e
guard is a skill published in the GitHub repository drn/dots (23 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 993 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (asks for root). 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…