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 onsager-ai/dev-skills --skill docs-drift-guardgit clone --depth 1 https://github.com/onsager-ai/dev-skillsWrote 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/onsager-ai/dev-skills/docs-drift-guard)<a href="https://agentmods.dev/skills/onsager-ai/dev-skills/docs-drift-guard"><img src="https://agentmods.dev/badge/skills/onsager-ai/dev-skills/docs-drift-guard/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/onsager-ai/dev-skills/docs-drift-guard"><img src="https://agentmods.dev/badge/skills/onsager-ai/dev-skills/docs-drift-guard.svg" alt="Reviewed on agentmods" width="80" 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.00548 |
| Opus 5.5 | $0.00017 | $0.00219 |
| Sonnet 5.5 | $0.00008 | $0.00110 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
docs-drift-guard 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 18d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation drift guard
Scope
This skill owns documentation method. The repo owns protected documents, generated outputs, check entrypoints and review requirements. A working link establishes path integrity, not that the surrounding claim is still true.
Prerequisites
Read AGENTS.md and the relevant doc's source/ownership rules. Identify the facts being described, their code/configuration source and existing tests/generators. Use harness-operations only when tool mapping is needed. Do not introduce a new dependency merely to run this skill.
Procedure
- Give each fact one authored home and link other consumers to it. Keep stable architecture intent in prose; derive API, CLI, configuration and mutable inventories from their owning source when possible.
- Prefer generated output with freshness checks, then executed examples, then deterministic structural checks, then explicit review of remaining prose. A generated artifact still needs a check against its source; generation alone does not guarantee freshness. Keep model-based semantic review advisory.
- Reuse the repo's existing link/path, doctest, snippet or architecture gate. If a new checker is needed, add it through the repo's dependency/CI process with a pinned version and prove it catches a broken reference or stale sample.
- For JavaScript repos adopting the maintained
docs-drift-check tool, use its
locked local binary via the owning package script or
npx --no-install docs-drift-check. Do not rely on an unpinned runtime download. External-link checks are a separate opt-in network axis, not an offline requirement. - Match higher checks to the claim: doctests for runnable examples; deterministic transclusion/freshness checks for code snippets; dependency rules for layering; path-triggered owner review for prose that cannot be mechanically derived.
- Edit the canonical source and regenerate outputs. Preserve ADR history through the repository's amendment convention. Do not make separate hand-edited copies of generated docs, common prompts or native skill projections.
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.
- 18d ago Changed · -40 lines · -154 tokens per session 055577de8194
- 1mo ago First seen · 90 lines · 196 tokens per session scan A d308a6d76b73
docs-drift-guard is a skill published in the GitHub repository onsager-ai/dev-skills (7 stars, last pushed 3d ago), licensed MIT. It adds 42 tokens to every session and 548 once invoked, about $0.0002 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-31.
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…