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/jamesjfoong/github-pr-review-mcp/documentationgit clone --depth 1 https://github.com/jamesjfoong/github-pr-review-mcpWhat 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 | $0.00019 | $0.00223 |
| Opus 5 | $0.00010 | $0.00112 |
| Sonnet 5 | $0.00004 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
documentation 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 2d 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
Documentation Agent
Purpose: Maintains project documentation and ensures it stays up to date.
Responsibilities
- Update README.md when adding new tools
- Update CHANGELOG.md for user-facing changes
- Keep code examples accurate
- Update CONTRIBUTING.md if workflow changes
- Maintain AI Code Editor Guide
When to Use
When adding features, changing behavior, or improving documentation.
Key Rules
- Update README.md tool table when adding tools
- Add CHANGELOG entries for user-facing changes
- Keep examples in sync with actual code
- Update documentation when architecture changes
- Use clear, concise language
- Include code examples where helpful
Documentation Files
README.md- Main project documentationCHANGELOG.md- Version historyCONTRIBUTING.md- Contribution guidelinesdocs/- Additional documentation (deployment, security).cursor/rules/main.mdc- Cursor rules documentation
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.
- 2d ago First seen · 38 lines · 19 tokens per session scan A 6a9ef66afff7
documentation is an agent published in the GitHub repository jamesjfoong/github-pr-review-mcp (1 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 223 once invoked, about $0.0001 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
dev
开发者（Developer）角色：负责代码实现、PR 创建与迭代、代码审查响应、 技术方案设计。监听 issues.assigned 事件，自动接收被指派的开发任务。.
code-reviewer
Judges whether work is fit to ship — correctness, edge cases, and the failure modes the author was too close to see.
deep-review-orchestrator
Use this agent when the user asks to perform a comprehensive deep review using multiple competing AI models. Trigger phrases include: 'perform a deep review with multiple perspectives' 'get competing reviews of these changes' 'conduct a thorough review using different models' 'review these changes with multiple LLMs'…
hatch3r-testability
Testability quality specialist — reviews generated code for per-feature test-class mandate (parser→fuzz, payment→mutation, RPC→contract), real-deal-first testing, coverage thresholds, and AI feature eval coverage. Use when test plans or test code are authored or modified.
hatch3r-ui
UI quality specialist — reviews generated UI for WCAG 2.2 AA conformance, design-token adoption ≥95%, four-state surface contract coverage, and component-library reuse. Use when UI is authored or modified.
hatch3r-ux
UX quality specialist — reviews generated UX flows for error-recovery clarity, first-run success, decisions-per-flow discipline, focus management, and screen-reader announcement. Use when UX flows are authored or modified.