agentmods.dev

docs-drift-maintenance

docs-drift-maintenance is a skill for Claude Code from chf3198/copilot-governance. It costs 34 tokens per session (664 once invoked), scanned A, original, MIT.

A maintenance check for documentation that may no longer match the code, configuration, workflows, user experience, or release process. Documentation drift means that written instructions have become inaccurate after changes.

In plain words
What is it for?
Use it after changing commands, configuration, APIs, workflows, or release steps, and before merging or releasing changes when documentation accuracy matters.
Why use it?
It prevents a feature from being considered complete when its related documentation is outdated or missing. It checks the applicable local, public, extension, release, and code-documentation surfaces.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

not rated 1 1mo ago A scan 34 tokens original MIT
View the source file chf3198/copilot-governance
Install

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.

agentmods
npx agentmods add skills/chf3198/copilot-governance/docs-drift-maintenance
Any agent
npx skills add chf3198/copilot-governance --skill docs-drift-maintenance
Clone the repo
git clone --depth 1 https://github.com/chf3198/copilot-governance

Made for: Claude Code.

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.

agentmods badge for docs-drift-maintenance

README.md
[![agentmods](https://agentmods.dev/badge/skills/chf3198/copilot-governance/docs-drift-maintenance.svg)](https://agentmods.dev/skills/chf3198/copilot-governance/docs-drift-maintenance)
Your own site
<a href="https://agentmods.dev/skills/chf3198/copilot-governance/docs-drift-maintenance"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/docs-drift-maintenance.svg" alt="Measured on agentmods" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 664 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.00664
Opus 5 $0.00017 $0.00332
Sonnet 5 $0.00007 $0.00133
Haiku 4.5 $0.00003 $0.00066

Measured 6d ago against content hash 7abba816175d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

docs-drift-maintenance 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 6d 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.

skills/docs-drift-maintenance/SKILL.md · 68 lines

How it starts

The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Docs Drift Maintenance

When to use

  • After any change to commands, config, workflows, API/CLI behavior, or release process.
  • Before merge/release if docs accuracy is part of acceptance.
  • Before declaring a feature complete (not just gates-complete).

Documentation coverage matrix (required)

For feature-adds and behavior changes, evaluate all applicable surfaces:

  1. Local operator docs
    • README.md
    • docs/technical/system-stability.md
    • docs/workflow/learnings.md
  2. Public repository docs
    • .github/CONTRIBUTING.md
    • .github/PULL_REQUEST_TEMPLATE.md
    • community profile files (CODE_OF_CONDUCT.md, SECURITY.md, SUPPORT.md) when behavior changes affect contributor workflow
  3. VS Code extension public profile
    • vscode-extension/README.md
    • vscode-extension/CHANGELOG.md
    • vscode-extension/package.json metadata/settings descriptions
  4. Release traceability docs
    • root CHANGELOG.md
    • release notes / GitHub release object
  5. Inline code documentation (added #101 — global linting governance)
    • JS/TS: JSDoc on all exported/public functions (@param, @returns, @description)
    • Python: Google-style docstrings on all public functions, classes, and modules
    • Bash: Header comment block on each script; inline comments on non-obvious logic
    • CSS: Section header comments; non-obvious rule explanations
    • Governed by lint-configs/eslint.config.devenv.js (JSDoc rules) and lint-configs/ruff.devenv.toml (D rules)
    • Drift check: run npm run lint:all; any new jsdoc/* or D* violations are inline-doc drift

Procedure

  1. Enumerate changed behavior/config/workflow/code surfaces.
  2. Map each change to impacted docs using the coverage matrix above.
  3. Identify stale, missing, or contradictory statements.
  4. Apply minimal doc deltas that restore correctness and traceability.
  5. Verify docs now match actual behavior and invocation paths.
  6. Record what was intentionally N/A and why.

Read the full file on GitHub · 68 lines

Changes

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.

  1. 6d ago First seen · 68 lines · 34 tokens per session scan A 7abba816175d

Subscribe to this mod's changes

docs-drift-maintenance is a skill published in the GitHub repository chf3198/copilot-governance (1 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 664 once invoked, about $0.0002 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-31.

Writing and docs
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens