A detailed review of a project's documentation against IDM standards. It checks whether key materials are present and also examines organization, intended readers, and documentation in the code.

Use it to assess a project's README, tutorials, API reference, changelog, document structure, audience fit, and code documentation.

It shows which information is missing, hard to find, aimed at the wrong audience, or poorly explained.

audit-docs — Skill for Claude Code by InstituteforDiseaseModeling

Install

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.

Claude Code

/plugin marketplace add InstituteforDiseaseModeling/idm_standards

Claude Code

/plugin install idm-standards

Made for: Claude Code.

Or install idm-standards, the plugin that ships this one along with the rest of its 10 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/institutefordiseasemodeling/idm_standards/audit-docs/github.svg)](https://agentmods.dev/skills/institutefordiseasemodeling/idm_standards/audit-docs)

Your own site

<a href="https://agentmods.dev/skills/institutefordiseasemodeling/idm_standards/audit-docs"><img src="https://agentmods.dev/badge/skills/institutefordiseasemodeling/idm_standards/audit-docs/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/institutefordiseasemodeling/idm_standards/audit-docs"><img src="https://agentmods.dev/badge/skills/institutefordiseasemodeling/idm_standards/audit-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 106 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,033 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00106	$0.03033
Opus 5	$0.00053	$0.01517
Sonnet 5	$0.00021	$0.00607
Haiku 4.5	$0.00011	$0.00303

Measured 10d ago against content hash 1e5941d3acb0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

audit-docs 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 10d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (assets/docs_templates/mkdocs_template/docs/customization/javascript/mathjax.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

idm_standards_plugin/skills/audit-docs/SKILL.md · 200 lines

How it starts

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

Documentation audit

Skill version: 2.1_2026.07.21

This skill performs a comprehensive documentation audit for an IDM project. It checks general completeness against the IDM documentation standards, then delegates to three specialized skills for deeper analysis, and assembles everything into a single prioritized report.

Workflow

Step 1: Identify the project and its documentation

Determine which project to audit. If the user specified a project, use that. Otherwise, use the current working directory.

The invocation may also supply a tier (1–3, per the IDM code tiers: 1 = library/DPG, 2 = small shared project, 3 = one-off) and a strictness (1 = report everything, the default; 2 = only findings that materially affect users — skip purely stylistic findings, e.g. report Vale errors but not suggestions). These are typically passed by the audit-project skill, which has already confirmed them with the user — do not re-ask in that case. If the tier is not supplied, infer it from the project (published package + CI → 1; tests + README → 2; scripts only → 3) and note the inferred tier in the report. Tier-conditional checks below ("for Tier 1/2 only") use this tier.

If the user provided any specific instructions when invoking this skill, integrate them into the workflow. For example, if they said "focus on the API reference" or "pay special attention to the README", make sure to emphasize those areas in your audit.

Discover the user config following $CLAUDE_PLUGIN_ROOT/reference/user-config.md (read it now), unless the invoking context (e.g. audit-project) already passed the directives in. Apply directives scoped to docs (audit-docs, audit-docs-structure, audit-personas, audit-docstrings, or untagged "all audits" directives) — a suppressed item is neither flagged as a weakness nor recommended. Directives can never waive a license violation or other hard-floor finding (see the reference). Exclude any config file and .claude/ from the docs being audited.

Read the full file on GitHub · 200 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

10d ago First seen · 200 lines · 106 tokens per session scan A 1e5941d3acb0

Subscribe to this mod's changes

audit-docs is a skill published in the GitHub repository InstituteforDiseaseModeling/idm_standards (2 stars, last pushed yesterday), licensed MIT. It adds 106 tokens to every session and 3,033 once invoked, about $0.0005 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

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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens