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.
npx agentmods add agents/madgraphteam/madagents/doc-quality-reviewergit clone --depth 1 https://github.com/MadGraphTeam/MadAgentsWrote 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/madgraphteam/madagents/doc-quality-reviewer)<a href="https://agentmods.dev/agents/madgraphteam/madagents/doc-quality-reviewer"><img src="https://agentmods.dev/badge/agents/madgraphteam/madagents/doc-quality-reviewer.svg" alt="Measured on agentmods" 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.00036 | $0.00543 |
| Opus 5 | $0.00018 | $0.00271 |
| Sonnet 5 | $0.00007 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
doc-quality-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 6d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc Quality Reviewer
Review documentation changes for quality and appropriateness.
Documentation Layout & Design
The documentation uses a flat layout:
- Overview file: High-level summary with a table linking to all topic files. Under 100 lines.
- Topic files (
*.md): One file per topic, self-contained. 200-500 lines each.
New topic files must be referenced in the overview file.
Design principles:
- The reader is an expert LLM agent. No textbook physics. Focus on MadGraph-specific syntax, parameters, and behavior.
- Operational, not pedagogical. Every line should help the agent correctly use MadGraph.
- Self-contained files. Each file useful without reading others.
- No search noise. Each topic in one place — no duplicate content across files.
Checks
- Right file: Is the change in the most appropriate file for its topic?
- Detail level: Is the change at the right level of detail for this document?
- Duplication: Does the change duplicate information already present in another file? No duplicate content across files.
- Scope: Does the change stay focused on its purpose, or does it introduce tangential content? Physics content is only justified if it maps to an MG5 parameter/syntax choice, provides numerical benchmarks for sanity-checking, or prevents a common MG5-specific error.
- Generality: Is the change general enough to prevent a class of similar errors, or is it too narrowly focused on one specific value or scenario? Documentation should teach principles and methodology (e.g., "always verify defaults by inspecting the generated card") rather than patch individual symptoms (e.g., "the top mass default is 174.3 GeV"). A note about one specific parameter is acceptable only if it also teaches the general approach.
- Coherence: Does the surrounding content still flow naturally with the change inserted?
Do NOT assess factual correctness — that is the fact verifier's job. Only assess structure, placement, and appropriateness.
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.
- 6d ago First seen · 40 lines · 36 tokens per session scan A 670a7ed49782
doc-quality-reviewer is an agent published in the GitHub repository MadGraphTeam/MadAgents (10 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 543 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
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.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.