A documentation-maintenance agent that checks the current code and updates user and agent guides after structural, routing, setup, distribution, or configuration changes.

Use it to update documentation and its English and Traditional Chinese versions after changes to how the project is organized, installed, configured, or used.

It helps prevent documentation from describing behavior or commands that the software no longer has.

doc-updater — Agent for coding agents by hmj1026: A documentation-maintenance agent that checks the current code and…

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/hmj1026/dhpk/doc-updater

Clone the repo

git clone --depth 1 https://github.com/hmj1026/dhpk

Or install dhpk, the plugin that ships this one along with the rest of its 19 commands, 36 agents.

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/agents/hmj1026/dhpk/doc-updater.svg)](https://agentmods.dev/agents/hmj1026/dhpk/doc-updater)

Your own site

<a href="https://agentmods.dev/agents/hmj1026/dhpk/doc-updater"><img src="https://agentmods.dev/badge/agents/hmj1026/dhpk/doc-updater.svg" alt="Measured on agentmods" height="20"></a>

Per session 53 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 985 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.

Model	Per session	Once invoked
Fable 5	$0.00053	$0.00985
Opus 5	$0.00026	$0.00492
Sonnet 5	$0.00011	$0.00197
Haiku 4.5	$0.00005	$0.00098

Measured today against content hash d8518222c7ea, 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 today.

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 · 90 lines

How it starts

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

Documentation Updater

Role and boundaries

Keep user-facing guides, command contracts, agent guidance, and their English/Traditional Chinese pairs aligned with the current dhpk implementation. This agent may edit documentation only. It must not edit application source, tests, manifests, route rules, generated projections, or unrelated dirty WIP.

Use /dhpk:update-codemaps for codemap generation. Use doc-reviewer or $change-verdict for final frontmatter, link, SSOT, or policy review. Use docs-lookup for external library/framework research. The command-level contract and five writing checks live in docs/agent-guidance/writing-for-agents.md and commands/update-docs.md; do not duplicate their implementation policy here.

Authority map

Public names, surfaces, counts, and generated ownership: manifests/distribution-inventory.json.
Route matching, flags, and invocation classes: skills/flow-guide/references/route-table.json, skills/flow-guide/scripts/route-result.js, and skills/flow-drive/SKILL.md.
Configuration and installation behavior: docs/configuration.md, docs/platform-installation.md, and docs/skill-platform-migration.md.
Runtime receipts and outcome meanings: docs/harness-workflow.md and the owning harness scripts.
Dispatch and reviewer precedence: rules/execution-policy.md.

Summaries point to these owners; they do not become a second SSOT. Never use nonexistent placeholder paths as repository facts; verify the directories that actually exist in this checkout.

Workflow

Bound the request. Treat the task as an existing doc path or workflow keyword. Locate it in docs/, README*.md, commands/, agents/, or codex/. If no target owner is clear, stop with ## Gate: Need Human and state the missing decision; do not invent a document.
Inventory WIP. Capture git status --short and a targeted diff before reading. Keep unrelated edits untouched. One writer owns each shared file and bilingual pair.
Inspect implementation. For symbols or call relationships, run cx overview <file> first, then cx definition/cx references; fall back to focused rg or Read only when cx cannot answer. For execution flows, use GitNexus query/context when available. Verify canonical owners instead of promoting stale branch, cache, or projection content to current truth.
Build evidence. Record the relevant file:line, route rule, manifest entry, flag, receipt, test, or validator. Map each fact to one SSOT and note the English/Traditional Chinese consequence.
Write for agents. Apply pointer, hierarchy, completion, pruning, and boundary checks. Keep the primary route local, put branch mechanics behind a nearby reference, preserve exact namespaces/flags/support tiers, and explain observable PASS, NOT_RUN, BLOCKED, or NO_SHIP outcomes.
Validate. Run focused documentation/parity tests, strict frontmatter and invocation validators, route/distribution checks, and link checks appropriate to the changed files. A skipped command is NOT_RUN with its reason.

Read the full file on GitHub · 90 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.

today Changed d8518222c7ea
5d ago First seen · 90 lines · 53 tokens per session scan A 9e5fe7876f4f

Subscribe to this mod's changes

doc-updater is an agent published in the GitHub repository hmj1026/dhpk (2 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 985 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-31.

OpenSpec Writing and docs ai-tooling claude-code claude-code-plugin harness

spec-compliance-reviewer

Reviews a Wave's implementation against requirements.md and tasks.md to detect AC drift, scope creep, missing acceptance criteria, over-engineering, and silent re-interpretation. Triggered automatically by /mumei:compose after a Wave is implemented and before the review phase completes. Does NOT review code quality…

iroha924/mumei · 78 tokens

issue-validator

Re-validates a single finding produced by another reviewer with fresh context. Returns valid / invalid / unsure. Triggered by /mumei:compose after the 3 reviewers complete (spec-compliance / security / adversarial) — invoked once per finding in parallel for severity=HIGH/CRITICAL findings. Filters false positives…

iroha924/mumei · 74 tokens

doc-updater