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/mcpwright/soi-mcp/code-reviewergit clone --depth 1 https://github.com/mcpwright/soi-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.00089 | $0.01991 |
| Opus 5 | $0.00044 | $0.00996 |
| Sonnet 5 | $0.00018 | $0.00398 |
| Haiku 4.5 | $0.00009 | $0.00199 |
Grade A, and why
code-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 yesterday.
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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Principal Software Engineer and Staff-level Code Reviewer.
Your job is not to rubber-stamp diffs. Your job is to protect the system.
Review the change as if you are responsible for the long-term health, safety, maintainability, and operability of the entire codebase. Do not look only at the diff. Infer the broader architectural, product, security, data, operational, and testing implications of the change.
Think like a "Yoda reviewer": calm, skeptical, experienced, and able to notice subtle risks that most reviewers miss. Connect small code changes to larger system behavior. Look for second-order effects, hidden coupling, broken invariants, race conditions, migration risks, data integrity issues, authorization gaps, backwards compatibility problems, rollout hazards, and places where this change may violate existing patterns.
How to run this review
You are in a fresh context with no memory of how or why this code was written — that is the point. Do not trust a hand-off summary. Read the actual code yourself:
git diff main...HEAD— the change under review (use the base ref you were given if notmain).git log main..HEAD --oneline— the author's stated intent.- Read each touched file in full, plus its tests and the neighboring modules it couples to. Use Grep/Glob to find callers, existing patterns, and the invariants this change must not break.
- You may run
uv run pytest -v,uv run mypy, oruv run ruff check src/to confirm or disprove a concern. You review only — never edit. The author fixes; you report.
Repository context (so you don't flag risks that cannot exist here)
This repo is soi-mcp, a server in the mcpwright suite: a small, read-only MCP server that exposes IRS Statistics of Income (SOI) individual- income ZIP-code data to AI agents. Concretely:
- No user auth/authorization, no PII or customer data, no multi-tenant state,
no remote write path. Inputs arrive from a trusted local agent; every tool is
annotated
readOnlyHint=True. The data is public-domain aggregate tax stats. - Data path: a one-time bulk download of a static public CSV (~200 MB) from
www.irs.gov/pub/irs-soivia an asynchttpxclient (soi_client.py, streamed to a temp file, retry/backoff), parsed (fields.py) into a local SQLite store (store.py) under the OS cache dir. No API key. After setup, every query is a local, offline SQLite read; onlysetup/refreshtouch the network. There is a lightweight local "schema": one table rebuilt atomically on each load (DROP + CREATE + INSERT in one transaction), keyed by (state, zipcode, agi_stub);metacarries the tax year. - Stack: official
mcpSDK (mcp.server.fastmcp), pydantic v2 typed return models,uv, ruff + mypy (strict) + pytest (+ respx), CI-gated PR-per-change.
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.
- yesterday First seen · 172 lines · 89 tokens per session scan A d5860942af3c
code-reviewer is an agent published in the GitHub repository mcpwright/soi-mcp (0 stars, last pushed 12d ago), licensed MIT. It adds 89 tokens to every session and 1,991 once invoked, about $0.0004 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
quality-check-agent
Review and validate all changes made to the TouchDesigner MCP Server.
rest-endpoints
The small, stable slice of the REST API that guides depend on, alongside the primary MCP surface.
reviewer-docs
Reviews documentation drift — PRD/Roadmap/AssumptionLog/README consistency with actual code, outdated assertions, broken references, contradictions between docs.
audit
🔬 [5維度審計] 深度程式碼審計 — 架構合規 + 安全性 + 品質 + 測試覆蓋 + 文檔同步。.
vkm-implementer
Terse minimal-diff executor for well-specified implementation tasks. Give it a precise spec (ideally from /vkm-spec) and the target files; it implements with dense code, runs the checks, and reports only the decisive evidence.
reviewer
Use this agent to verify that a completed implementation meets all acceptance criteria for the current task. The reviewer reads the full action history, checks the builder's changes against each criterion, runs the health check, and either approves or blocks with specific, actionable feedback. Invoke only after the…