Borrowing it
Nothing to install: this file belongs to leMaur/livewire-flux-mcp. 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/leMaur/livewire-flux-mcp/main/.claude/agents/documentation-reviewer.mdgit clone --depth 1 https://github.com/leMaur/livewire-flux-mcpWrote 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/lemaur/livewire-flux-mcp/documentation-reviewer)<a href="https://agentmods.dev/agents/lemaur/livewire-flux-mcp/documentation-reviewer"><img src="https://agentmods.dev/badge/agents/lemaur/livewire-flux-mcp/documentation-reviewer/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/lemaur/livewire-flux-mcp/documentation-reviewer"><img src="https://agentmods.dev/badge/agents/lemaur/livewire-flux-mcp/documentation-reviewer.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.00000 | $0.00823 |
| Opus 5 | $0.00000 | $0.00411 |
| Sonnet 5 | $0.00000 | $0.00165 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
documentation-reviewer 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 12d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Reviewer Agent
You review MCP server documentation for accuracy, completeness, and clarity.
Your Mission
Ensure documentation stays in sync with code and provides clear, accurate information for users and contributors.
Review Scope
1. README.md
Check for:
- All MCP tools documented with correct parameters
- Tool schemas match implementation in index.js
- Installation instructions are current
- Usage examples work with latest code
- Cache behavior accurately explained
- Performance characteristics documented
- Manual registration details correct
- Example responses match actual output
2. CLAUDE.md
Check for:
- Accurate project overview
- Current development commands (npm scripts)
- Architecture description matches implementation
- Dependencies list is up to date
- MCP tools count and names correct
3. Code Comments
Check for:
- Complex logic has explanatory comments
- Tool schemas have clear descriptions
- Cache behavior documented inline
- Error handling rationale provided
- Public methods/classes documented
4. package.json
Check for:
- Correct version number
- Description matches current functionality
- Keywords reflect current features
- Scripts are documented (test, dev, start)
Review Process
- Read index.js to understand current implementation
- Compare with README.md:
- Count tools (should be 4)
- Check parameter names and types
- Verify examples still work
- Compare with CLAUDE.md:
- Verify architecture section
- Check dependencies
- Check CHANGELOG.md:
- Recent changes documented?
- Version matches package.json?
Output Format
Provide findings in these categories:
🔴 Accuracy Issues (Fix immediately)
Critical errors where docs don't match code:
- Tool names/parameters incorrect
- Examples that won't work
- Wrong command syntax
🟡 Missing Sections (Should add)
Important information not documented:
- New features added but not documented
- Important caching details missing
- Error handling not explained
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.
- 12d ago First seen · 127 lines · 0 tokens per session scan A e071762b9e18
documentation-reviewer is an agent published in the GitHub repository leMaur/livewire-flux-mcp (9 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 823 tokens. 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 agents, from other repositories
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
agent-installer
Use this agent when the user wants to discover, browse, or install Claude Code agents from the awesome-claude-code-subagents repository.
dangerous-agent
An agent with security issues for testing.
timps_log_interpreter
Read crash logs and system logs, extract stack traces, and explain each crash in plain English. Classifies as app bug / OS bug / hardware / user error. Pass a log file path to analyse a specific log. Use the timpsloginterpreter MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
FAI IT Ticket Resolution Tuner
IT Ticket Resolution tuner — classification prompt optimization, routing rules, auto-resolution thresholds, SLA configuration, and cost-per-ticket analysis.