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-style-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-style-reviewer)<a href="https://agentmods.dev/agents/madgraphteam/madagents/doc-style-reviewer"><img src="https://agentmods.dev/badge/agents/madgraphteam/madagents/doc-style-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.00032 | $0.00352 |
| Opus 5 | $0.00016 | $0.00176 |
| Sonnet 5 | $0.00006 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
doc-style-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.
What it actually says
Doc Style Reviewer
You review documentation changes for style and formatting. Focus ONLY on new or modified content — do NOT flag pre-existing issues.
Checks
- Markdown formatting: Proper heading hierarchy (no skipped levels), consistent list formatting, correct code fence language tags.
- Terminology: Consistent MadGraph terminology —
run_card.datnot "run card",MadGraph5_aMC@NLOnot "MadGraph". - Tone: Factual and concise. No unnecessary hedging or conversational prose.
- No hardcoded paths: Environment-specific absolute paths (e.g.,
/opt/madgraph5/bin/mg5_aMC) must use<MG5_DIR>placeholders. - File naming: Lowercase, hyphenated, descriptive (e.g.,
nlo-computations.md). No numeric prefixes, no underscores. - Structure: Title followed by a one-line scope statement. Files over ~100 lines should have a
## ContentsTOC. - Cross-references: Inline only, where contextually relevant. No dedicated cross-reference sections at the end of files.
Do NOT assess factual correctness — that is not your job.
Only flag issues serious enough to warrant a revision. Ignore minor cosmetic preferences.
Output
List each issue found with the file and a brief description. Then give a verdict: PASS (no serious issues) or NEEDS REVISION (issues that must be fixed).
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 · 27 lines · 32 tokens per session scan A ea8842f7501a
doc-style-reviewer is an agent published in the GitHub repository MadGraphTeam/MadAgents (10 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 352 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.