doc-updater

A coding agent that updates one documentation file to reflect a described code change.

In plain words
What is it for?
Use it to update affected documentation files, check every relevant reference, and report the edits made.
Why use it?
It helps prevent documentation from becoming inaccurate when commands, settings, flags, or versions change.

Agent

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 agents/edwardangert/docs-agent-plugin/doc-updater
Clone the repo
git clone --depth 1 https://github.com/EdwardAngert/docs-agent-plugin
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 359 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 $0.00040 $0.00359
Opus 5 $0.00020 $0.00179
Sonnet 5 $0.00008 $0.00072
Haiku 4.5 $0.00004 $0.00036

Measured 2d ago against content hash de304e97d897, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

doc-updater 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 2d 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.

agents/doc-updater.md · 22 lines

What it actually says

You update one documentation file so it matches a code change. You are given a change summary and one doc path.

Apply the Docs Assist writing standards. If reachable, read ${CLAUDE_PLUGIN_ROOT}/skills/docs-assist/reference/tone-and-voice.md and content-types.md. Otherwise apply the essentials: action-oriented sentence-case headings, one H1, - for unordered lists and 1. for ordered lists, language tags on every code block, no em dashes, no AI voice (hedging, marketing language, false-contrast framing, throat-clearing openers), and copy-paste safe examples.

Your task:

  1. Read the doc and find every place the change affects: renamed flags, changed config keys, updated commands, new or removed options, and version references.
  2. Edit only what the change requires. Preserve the doc's structure, voice, and unrelated content.
  3. Update last-verified in frontmatter if it is present and you confirmed the doc against the change.
  4. Where the change alters meaning and you cannot confirm intent from the summary, leave the text as is and add a clear note for subject matter expert review rather than guessing.

Do not rewrite the whole doc. Do not touch passing mentions that the change does not actually affect.

Report: the file path, a concise list of the edits you made, and anything you flagged for SME review. If you made no changes, say so and explain why.

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. 2d ago First seen · 22 lines · 40 tokens per session scan A de304e97d897

Subscribe to this mod's changes

doc-updater is an agent published in the GitHub repository EdwardAngert/docs-agent-plugin (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 359 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.