Borrowing it
Nothing to install: this file belongs to InstituteforDiseaseModeling/idm_standards. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/InstituteforDiseaseModeling/idm_standards/main/.claude/skills/update-docs-plugin/SKILL.mdgit clone --depth 1 https://github.com/InstituteforDiseaseModeling/idm_standardsWrote 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/institutefordiseasemodeling/idm_standards/update-docs-plugin)<a href="https://agentmods.dev/skills/institutefordiseasemodeling/idm_standards/update-docs-plugin"><img src="https://agentmods.dev/badge/skills/institutefordiseasemodeling/idm_standards/update-docs-plugin/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/institutefordiseasemodeling/idm_standards/update-docs-plugin"><img src="https://agentmods.dev/badge/skills/institutefordiseasemodeling/idm_standards/update-docs-plugin.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.00123 | $0.02425 |
| Opus 5.5 | $0.00049 | $0.00970 |
| Sonnet 5.5 | $0.00025 | $0.00485 |
| Haiku 4.5 | $0.00012 | $0.00243 |
Grade A, and why
update-docs-plugin 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 2mo 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update the idm-standards docs skills from docs_guidance
The documentation skills in idm_standards_plugin/skills/ (audit-docs, audit-docs-structure, audit-personas, audit-docstrings) are derived from, and must stay consistent with, the source documentation in docs_guidance/. When the guidance changes, these skills need to learn those changes — otherwise the plugin drifts from the project's actual documentation standards and the audit/review skills give stale advice.
Exception — audit-docstrings: this skill's content is sourced from eng_guidance/4_documentation.md, not docs_guidance/ (docs_guidance/topic-types/reference.md itself points there for docstring guidance). If you're doing a general sync pass, also diff eng_guidance/4_documentation.md over the same range and propagate changes to audit-docstrings alongside whatever docs_guidance/ changes you find — don't skip it just because it's outside docs_guidance/. This is also covered from the other direction by idm_standards_plugin/admin/update_prompt.md (step 2c); if that pass already ran for this range, don't duplicate the edit.
The audit-docs skill also ships the canonical Vale config and reference docs templates — vale.ini, styles/, and docs_templates/ — under idm_standards_plugin/skills/audit-docs/assets/. An installed plugin only ships the idm_standards_plugin/ directory, so these live inside it where the skill can read them at runtime. These are the only copies (the repo formerly duplicated them at the repo root, but those were removed); edit them directly in place. A change to any of them is a behavior change to audit-docs and counts toward the version bump and changelog (see step 6b).
This skill walks you through that sync: identify what changed, figure out which plugin skills need updating, propose the edits, apply them, bump the version, and update the changelog.
Workflow
1. Determine the diff range
If the user specified a commit, commit range, or date range in their request, use that. Otherwise default to "since the last release": the diff range is the commit that set the current plugin version → HEAD.
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.
- 2mo ago First seen · 154 lines · 123 tokens per session scan A 5854326803af
update-docs-plugin is a skill published in the GitHub repository InstituteforDiseaseModeling/idm_standards (2 stars, last pushed 9d ago), licensed MIT. It adds 123 tokens to every session and 2,425 once invoked, about $0.0005 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…