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 deploy-auditgit 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/deploy-audit)<a href="https://agentmods.dev/skills/drn/dots/deploy-audit"><img src="https://agentmods.dev/badge/skills/drn/dots/deploy-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/drn/dots/deploy-audit"><img src="https://agentmods.dev/badge/skills/drn/dots/deploy-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00076 | $0.01384 |
| Opus 5.5 | $0.00030 | $0.00554 |
| Sonnet 5.5 | $0.00015 | $0.00277 |
| Haiku 4.5 | $0.00008 | $0.00138 |
Grade A, and why
deploy-audit 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 1mo 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Deploy Risk Audit
Audit the commits pending between a base branch and a deployed branch/tag, assess the risk of each change, and open the GitHub compare diff for human review. This is an informational audit — it does not block or change anything on its own.
Arguments
$ARGUMENTS- Optional:<base>..<deployed>(e.g.master..production), or just the deployed ref if the base is the repo's default branch. If omitted, detect candidates from context below and ask the user to confirm.
Context
- Remote: !
git remote get-url origin 2>/dev/null | head -1 - Default branch: !
git branch -r 2>/dev/null | grep -oE 'origin/(main|master)' | head -1 - Remote branches: !
git branch -r 2>/dev/null | grep -viE 'HEAD|dependabot' | head -30 - Recent tags: !
git tag --sort=-creatordate 2>/dev/null | head -10
Instructions
Work through the following steps in order, gathering enough evidence at each one to give the final risk report real teeth rather than a generic checklist.
Step 1: Determine the two refs
Parse $ARGUMENTS for <base>..<deployed>. If only one ref is given, treat it
as the deployed ref and use the detected default branch as base. If nothing is
given, look at the remote branches/tags in Context above for likely
candidates (a production/release/deploy branch, or the most recent tag)
and ask the user to confirm the base and deployed refs before proceeding.
Refs and the org/repo derived from the remote URL are treated as untrusted
input for shell purposes: if either contains characters outside
[A-Za-z0-9._/-], do not interpolate it directly into a shell command —
quote it and confirm with the user first.
Run git fetch origin for both refs to ensure they are current.
Step 2: Enumerate pending commits
git log --oneline <deployed>..<base>
git diff --stat <deployed>..<base>
If this returns nothing, report "Nothing pending — <deployed> and <base>
are in sync" and stop.
Read full commit messages for risk signal:
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.
- 1mo ago Changed · +1 lines b3a3abc3f336
- 1mo ago First seen · 144 lines · 76 tokens per session scan A 299591d3a2fb
deploy-audit is a skill published in the GitHub repository drn/dots (23 stars, last pushed 11d ago), licensed MIT. It adds 76 tokens to every session and 1,384 once invoked, about $0.0003 per session on Opus 5.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
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…
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…
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…