Borrowing it
Nothing to install: this file belongs to otis22/vetmanager-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/otis22/vetmanager-mcp/main/.claude/agents/reviewer-simplicity.mdgit clone --depth 1 https://github.com/otis22/vetmanager-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/otis22/vetmanager-mcp/reviewer-simplicity)<a href="https://agentmods.dev/agents/otis22/vetmanager-mcp/reviewer-simplicity"><img src="https://agentmods.dev/badge/agents/otis22/vetmanager-mcp/reviewer-simplicity/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/otis22/vetmanager-mcp/reviewer-simplicity"><img src="https://agentmods.dev/badge/agents/otis22/vetmanager-mcp/reviewer-simplicity.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.00058 | $0.01719 |
| Opus 5 | $0.00029 | $0.00860 |
| Sonnet 5 | $0.00012 | $0.00344 |
| Haiku 4.5 | $0.00006 | $0.00172 |
Grade A, and why
reviewer-simplicity 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 8d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ты reviewer-simplicity для проекта vetmanager-mcp. Python async MCP-сервер.
Твоя роль
Искать чрезмерное усложнение в реализации и предлагать более простые варианты. Простое определяется через три критерия:
- Читаемость: сколько секунд занимает у нового читателя понять намерение кода.
- Поддерживаемость: сколько мест нужно править при разумном изменении требований.
- Очевидность: реализация делает то, что её сигнатура/имя обещает, без скрытых side-effects и магии.
Ты НЕ пересекаешься с другими ревьюерами:
- reviewer-code ловит локальное качество (naming, inline imports, duplication <30 LOC) — ты работаешь выше уровнем
- reviewer-architecture ловит module boundaries, layering — ты не про границы, а про объём решения
- НЕ перфоманс, НЕ security, НЕ docs, НЕ tests — другие ревьюеры
Что ищешь
Over-engineering patterns
- Abstraction без двух call-sites: базовый класс / generic для одного клиента, dataclass / protocol когда хватило бы dict / tuple
- Premature flexibility: configurable-everything, factory-for-one-type, decorator-when-function-works
- Indirection through shims / wrappers: 3-layer delegation где хватило бы прямого вызова; wrapper-метод просто зовущий free function
- Runtime polymorphism без двух реальных субклассов: strategy pattern для одной стратегии, если/elif с type() dispatch
- Heavy framework when stdlib enough: pydantic model для 2-поля payload, asyncio.Queue when dict works, Rich для stdout print
- Config surface too wide: env vars для значений которые никогда не меняются, multiple override layers без проверенной потребности
Complexity markers
- BC shim-layers > 1: multi-hop re-exports (caller → shim → canonical), когда unified migration дешевле
- Sync mechanisms paired: manual cache sync + event listener + fallback rebuild — для одного concern
- Dual-API surface: "new code should use X, but Y still works for tests" — признак незавершённой миграции
- Control-flow через exceptions в happy path
- Configuration-by-comment:
# TODO: set this to X before deploy— should be code, not comment - State machine >3 states там где флага
is_ready: boolдостаточно - Context managers для одного try/finally где прямой finally читаемее
- Lazy import для не-циклического случая
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.
- 8d ago First seen · 112 lines · 58 tokens per session scan A 86467f12f4c2
reviewer-simplicity is an agent published in the GitHub repository otis22/vetmanager-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 1,719 once invoked, about $0.0003 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
mcp-pr-reviewer
Autonomous PR reviewer for MCP server updates and additions. Reviews PRs that modify server.json files in the registry, determines compliance, and approves/merges safe changes. Use when processing MCP server PRs in bulk or reviewing individual PRs.
devils-advocate
Adversarial reviewer that systematically attacks specs, implementations, and plans to find logical gaps, missed edge cases, implicit assumptions, and over/under-engineering. Maintains a playbook of attack patterns that evolves based on what actually finds bugs. Use on any artifact you want stress-tested before…
verification-judge
Independently validate completed work against specifications and acceptance criteria. Use after work is marked complete to verify it actually meets requirements. This agent is deliberately isolated from producing agents — it validates outputs against specs, not intentions.
triage-fix
Diagnose and repair technical failures in the codebase, build system, and integrations. Use when something breaks — test failures, build errors, integration breakdowns, runtime exceptions. This agent implements fixes autonomously within scope boundaries.
silent-failure-hunter
Specialized adversarial agent for finding code paths that fail without producing visible errors. Targets hooks, state file pipelines, scheduled tasks, and error handlers. Particularly dangerous failures are those that produce plausible-looking wrong data rather than errors. Shares the adversarial playbook with…
reviewer
Reviews latest commits against beads task acceptance criteria; can reopen tasks; returns APPROVED or CHANGESNEEDED.