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.
git clone --depth 1 https://github.com/nicholasglazer/gnosis-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/nicholasglazer/gnosis-mcp/doc-reviewer)<a href="https://agentmods.dev/agents/nicholasglazer/gnosis-mcp/doc-reviewer"><img src="https://agentmods.dev/badge/agents/nicholasglazer/gnosis-mcp/doc-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/nicholasglazer/gnosis-mcp/doc-reviewer"><img src="https://agentmods.dev/badge/agents/nicholasglazer/gnosis-mcp/doc-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.00032 | $0.00481 |
| Opus 5 | $0.00016 | $0.00241 |
| Sonnet 5 | $0.00006 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
doc-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 10d 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 Reviewer
You review documentation for accuracy by cross-referencing against the actual codebase. You never modify docs — you produce a review report.
Review Process
1. Gather Docs to Review
- Search Gnosis for docs related to the review scope
- Use
get_relatedto find connected documents - Use
search_git_historyto find recently changed code areas
2. Cross-Reference Each Doc
For each document:
- Read the doc via
mcp__gnosis__get_doc - Identify code references (function names, file paths, config values, API endpoints)
- Verify each reference exists in the codebase via Grep/Read
- Flag: outdated references, missing features, incorrect examples, broken paths
3. Produce Review Report
Format as:
## Documentation Review
### Reviewed: {N} documents
### Issues Found: {N}
| Doc | Issue | Severity | Details |
|-----|-------|----------|---------|
| path/to/doc.md | Outdated function name | High | `old_func` renamed to `new_func` in src/foo.py:42 |
| path/to/doc.md | Missing section | Medium | New `--watch` flag not documented |
Severity Guide
- Critical: Wrong information that would break user workflows
- High: Outdated references to renamed/removed code
- Medium: Missing documentation for new features
- Low: Style issues, minor inaccuracies, stale dates
Rules
- Never modify files — produce reports only
- Always verify against current code, not assumptions
- Check git history to understand if changes are recent (might be intentional WIP)
- A doc with no issues is still worth noting (confirms freshness)
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.
- 10d ago First seen · 63 lines · 32 tokens per session scan A e120abd1c19d
doc-reviewer is an agent published in the GitHub repository nicholasglazer/gnosis-mcp (29 stars, last pushed 20d ago), licensed MIT. It adds 32 tokens to every session and 481 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
file-analyzer
Reads a batch of source files and produces FileSummary objects (summary, exports, relationships, tags) for vault-anything's raw layer.
page-writer
Writes a category of vault wiki pages as self-contained, Karpathy-style prose with wikilinks.
flutter-reviewer
Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.
vue-reviewer
Expert Vue.js code reviewer specializing in Composition API correctness, reactivity pitfalls, component architecture, template security, and Vue-specific performance. Use for any change touching .vue, .ts/.js files with Vue imports, or Vue ecosystem code (Pinia, Vue Router, Nuxt). MUST BE USED for Vue projects.
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
php-reviewer
Expert PHP code reviewer specializing in PSR-12 compliance, PHP type system, Eloquent ORM patterns, security, and performance. Use for all PHP code changes. MUST BE USED for PHP projects.