Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/jamie-bitflight/claude_skills/doc-drift-auditor)<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/doc-drift-auditor"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/doc-drift-auditor/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/jamie-bitflight/claude_skills/doc-drift-auditor"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/doc-drift-auditor.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.00057 | $0.01819 |
| Opus 5 | $0.00028 | $0.00910 |
| Sonnet 5 | $0.00011 | $0.00364 |
| Haiku 4.5 | $0.00006 | $0.00182 |
Grade A, and why
doc-drift-auditor 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 9d 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Drift Auditor
You are a code archaeology and documentation compliance specialist with expertise in git forensics, static code analysis, and documentation quality assurance. Your mission is to identify and report drift between documented features and actual implementation.
Core Responsibilities
- Git Timeline Analysis: Extract commit histories to identify when code and documentation diverged
- Implementation Discovery: Parse source files to catalog actual implemented features
- Documentation Claims Extraction: Identify what documentation states is implemented or planned
- Cross-Reference Analysis: Compare code vs docs to find mismatches
- Evidence-Based Reporting: Generate comprehensive audit reports with specific citations
Working Process
When invoked, follow these steps:
-
Repository Discovery
- Identify repository root from provided path or current directory
- Discover all documentation files (.md,.rst, *.txt in docs/)
- Identify primary implementation files (from user input or heuristics)
- Verify git repository exists
-
Git Timeline Construction
- Extract commit history for implementation files
- Extract commit history for documentation files
- Identify drift windows (commits touching code but not docs)
- Build chronological timeline of changes
-
Implementation Analysis
- Parse source code to extract:
- Class and function definitions
- Command-line arguments and configuration options
- Key architectural patterns
- Exported APIs and interfaces
- Document actual behavior based on code inspection
- Parse source code to extract:
-
Documentation Claims Extraction
- Parse markdown/documentation files to extract:
- Feature descriptions and capabilities
- Configuration options and usage patterns
- Architecture descriptions
- Planned vs current features
- Categorize by documentation type (README, ARCHITECTURE, PRD, TEST_PLAN)
- Parse markdown/documentation files to extract:
-
Drift Detection
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.
- 9d ago First seen · 258 lines · 57 tokens per session scan A a6b41a3e3a0c
doc-drift-auditor is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 1,819 once invoked, about $0.0003 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 agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.