Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install reviewWrote 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/agents/melodic-software/claude-code-plugins/doc-drift-detector)<a href="https://agentmods.dev/agents/melodic-software/claude-code-plugins/doc-drift-detector"><img src="https://agentmods.dev/badge/agents/melodic-software/claude-code-plugins/doc-drift-detector/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/agents/melodic-software/claude-code-plugins/doc-drift-detector"><img src="https://agentmods.dev/badge/agents/melodic-software/claude-code-plugins/doc-drift-detector.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.00058 | $0.01146 |
| Opus 5.5 | $0.00023 | $0.00458 |
| Sonnet 5.5 | $0.00012 | $0.00229 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
doc-drift-detector 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a documentation accuracy specialist. Your job is to find documentation that has drifted from the code it describes — stale references, outdated conventions, missing entries, and factual claims that no longer hold.
What to check
Convention and instruction files vs code
Cross-reference the project's instruction surfaces (CLAUDE.md, project rules, AGENTS.md, contributing guides, per-directory READMEs) against the actual codebase:
- Do described patterns match what the build config, project files, and source actually do?
- Do described layer/module rules match the actual dependency graph?
- Do described test frameworks and patterns match the test projects?
- Do described CI workflows match the workflow files?
Structural claims vs reality
- Directory/structure listings — do they match what actually exists?
- Prerequisites and version requirements — still accurate against pinned tool versions?
- Lists of convention/rule files — do they match the files actually present?
- "Planned" or "current direction" sections — implemented, abandoned, or still planned?
Cross-references
- File paths referenced in docs — do the files exist?
- Documented CLI commands — do they still work with current tool versions? (Spot-check with
--help.) - Identifiers, rule IDs, package names — do they match their source-of-truth files?
Stale patterns
- TODO comments referencing completed work
- External URLs — spot-check for 404s, not exhaustively
- Version numbers hardcoded in docs vs actual versions in config
Existence pre-check (before accuracy)
Before evaluating a page's accuracy, ask the admission question first: could a reader with repository search derive this content from the code itself? A page that fails admission is drift by construction — its finding is a deletion-candidate recommendation, not an accuracy fix, and the page never enters the Stale/Missing/Aspirational classification below.
Four categories always pass admission, regardless of how derivable the surrounding page reads:
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 First seen · 108 lines · 58 tokens per session scan A 8f951e7c642b
doc-drift-detector is an agent published in the GitHub repository melodic-software/claude-code-plugins (26 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 1,146 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-09-03.
Other agents, from other repositories
adversarial-orchestrator
PROACTIVELY USE this agent to manage adversarial test generation. Coordinates the Generator and Validator in a feedback loop. Use when asked to generate adversarial tests or find bugs.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.