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.
curl -O https://raw.githubusercontent.com/magendooro/n98-magerun2-performance-review/main/.claude/agents/documentation-updater.mdgit clone --depth 1 https://github.com/magendooro/n98-magerun2-performance-reviewWrote 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/agents/magendooro/n98-magerun2-performance-review/documentation-updater)<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.
<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>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 | $0.00024 | $0.01246 |
| Sonnet 5 | $0.00010 | $0.00498 |
| Haiku 4.5 | $0.00005 | $0.00249 |
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 11d 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 — 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
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.
- 11d ago First seen · 481 lines · 48 tokens per session scan A b04658330006
documentation-updater is an agent published in the GitHub repository magendooro/n98-magerun2-performance-review (22 stars, last pushed 9mo ago), licensed MIT. It adds 48 tokens to every session and 2,492 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.