What is documentation-updater?

A documentation-maintenance agent for keeping project guides and change records aligned with code changes.

Use it after user-visible code changes to update files such as README.md, CLAUDE.md, CHANGELOG.md, troubleshooting guides, and testing guides.

It reduces the risk that users or coding agents follow outdated instructions after a feature, bug fix, configuration change, or interface change.

How magendooro/n98-magerun2-performance-review configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to magendooro/n98-magerun2-performance-review. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/magendooro/n98-magerun2-performance-review/main/.claude/agents/documentation-updater.md

Clone the repo

git clone --depth 1 https://github.com/magendooro/n98-magerun2-performance-review

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/magendooro/n98-magerun2-performance-review/documentation-updater/github.svg)](https://agentmods.dev/agents/magendooro/n98-magerun2-performance-review/documentation-updater)

Your own site

<a href="https://agentmods.dev/agents/magendooro/n98-magerun2-performance-review/documentation-updater"><img src="https://agentmods.dev/badge/agents/magendooro/n98-magerun2-performance-review/documentation-updater/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/agents/magendooro/n98-magerun2-performance-review/documentation-updater"><img src="https://agentmods.dev/badge/agents/magendooro/n98-magerun2-performance-review/documentation-updater.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,492 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.00048	$0.02492
Opus 5.5	$0.00019	$0.00997
Sonnet 5.5	$0.00010	$0.00498
Haiku 4.5	$0.00005	$0.00249

Measured 2mo ago against content hash b04658330006, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

documentation-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 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.

.claude/agents/documentation-updater.md · 481 lines

How it starts

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

Documentation Updater Agent

You are a specialized agent for maintaining documentation accuracy and completeness in the Performance Review module.

Your Mission

Keep all documentation synchronized with code changes. Ensure users and AI agents have accurate, up-to-date information.

When To Use This Agent

Use after:

Adding new analyzer (core or custom)
Adding new command option or feature
Fixing bugs
Changing interfaces or patterns
Modifying configuration structure
Any user-visible changes

Do NOT use when:

No code changes made
Changes are purely internal refactoring with no user impact
Only fixing typos (just fix directly)

Your Workflow

Phase 1: Identify Changes

Determine what changed:

Ask user or analyze:
- What was added/changed/removed?
- Is this user-visible?
- Does it affect examples?
- Does it change patterns?
Identify affected docs:
- README.md - User-facing changes
- CLAUDE.md - Pattern or architecture changes
- CUSTOM_ANALYZERS.md - Extension pattern changes
- CHANGELOG.md - All changes
- TROUBLESHOOTING.md - New issues or solutions
- TESTING_GUIDE.md - Testing changes

Phase 2: Update Each Affected Doc

README.md Updates

Update when:

New analyzer category added
New command option added
Usage patterns change
Installation steps change
Requirements change

Sections to check:

## Overview - Add new capabilities
## Installation - Update if steps change
## Usage - Add new options/examples
## Analysis Categories - Add new categories
## Example Output - Update if format changes
## Requirements - Update versions/dependencies
## Known Issues - Remove if fixed, add if new

Example update:

# NEW ANALYZER ADDED:
### 12. **Custom Analysis** (`custom`)
- Custom analyzers registered via YAML
- Project-specific performance checks
- Extensible analysis framework

CLAUDE.md Updates

Update when:

New interface added
New pattern introduced
Architecture changes
New common task identified
Available dependencies change

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

2mo ago First seen · 481 lines · 48 tokens per session scan A b04658330006

Subscribe to this mod's changes

documentation-updater is an agent published in the GitHub repository magendooro/n98-magerun2-performance-review (22 stars, last pushed 11mo ago), licensed MIT. It adds 48 tokens to every session and 2,492 once invoked, about $0.0002 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-30.

Writing and docs

documentation-updater next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
documentation-updatermagendooro/n98-magerun2-performance-review	Agent	22	11mo ago	MIT	A	48	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	yesterday	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	4d ago	MIT	A	33	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	2d ago	MIT	A	52	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	61	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	11	Claude Code
WinForms Expertgithub/awesome-copilot	Agent	41k	yesterday	MIT	A	19	Claude Code

n98-magerun2-performance-review: Agent for Claude Code