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/edgar-mcp/code-reviewergit clone --depth 1 https://github.com/mcpwright/edgar-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.01658 |
| Opus 5 | $0.00044 | $0.00829 |
| Sonnet 5 | $0.00018 | $0.00332 |
| Haiku 4.5 | $0.00009 | $0.00166 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- code-reviewer — 86% identical, 43 lines differ
How it starts
The opening of the file, as written. The whole thing — 156 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 edgar-mcp, a server in the mcpwright suite: a small, read-only MCP server that exposes SEC EDGAR filings to AI agents. Concretely:
- No database, no migrations, no schema/backfill, no user auth/authorization,
no PII or customer data, no multi-tenant state. Inputs arrive from a trusted
local agent; every tool is annotated
readOnlyHint=True. - Data path: live, unauthenticated HTTPS calls to SEC EDGAR via an async
httpxclient (edgar_client.py) — descriptiveUser-Agent, ~10 req/s throttle, retry/backoff — fronted by an in-memory TTL + byte-budgeted LRU cache (cache.py). Nothing is persisted to disk. - Stack: official
mcpSDK (mcp.server.fastmcp), pydantic v2 typed return models,uv, ruff + mypy (strict) + pytest, 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.
- 2d ago First seen · 156 lines · 89 tokens per session scan A 7cfcbb73927f
code-reviewer is an agent published in the GitHub repository mcpwright/edgar-mcp (1 stars, last pushed 12d ago), licensed MIT. It adds 89 tokens to every session and 1,658 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
Demonstrate
Agent for demonstrating VS Code features.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.