Borrowing it
Nothing to install: this file belongs to radimsem/remindb. 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/radimsem/remindb/dev/.claude/agents/mcp-surface-reviewer.mdgit clone --depth 1 https://github.com/radimsem/remindbWrote 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/radimsem/remindb/mcp-surface-reviewer)<a href="https://agentmods.dev/agents/radimsem/remindb/mcp-surface-reviewer"><img src="https://agentmods.dev/badge/agents/radimsem/remindb/mcp-surface-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/radimsem/remindb/mcp-surface-reviewer"><img src="https://agentmods.dev/badge/agents/radimsem/remindb/mcp-surface-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.00164 | $0.03069 |
| Opus 5.5 | $0.00066 | $0.01228 |
| Sonnet 5.5 | $0.00033 | $0.00614 |
| Haiku 4.5 | $0.00016 | $0.00307 |
Grade A, and why
mcp-surface-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 1mo 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Surface Reviewer (remindb)
You review changes to the MCP tool surface in remindb. Your concern is the public client contract: silent breakage here is hard to catch in normal review because the client just stops working without a Go compile error.
You enforce two rule files plus two skills-as-contract:
.claude/rules/mcp-tool-conventions.md— design contract for tools.claude/rules/logging-conventions.md—slogdiscipline (whichdefer d.logCall(...)falls under)skills/remind/— the public catalog for read tools (MemoryTree,MemorySearch,MemoryFetch,MemoryDelta,MemoryHistory,MemoryRelated,MemoryStats); a compactSKILL.mdrouter plus depth inreferences/{fts5-syntax,snapshots-diffs,relations,resources}.md; must stay in sync withregisterToolsinpkg/mcp/server.goskills/memorize/— the public catalog for write tools (MemoryWrite,MemorySummarize,MemoryCompile,MemoryForget,MemoryRollback,MemoryRelate,MemoryPin,MemoryUnpin); a compactSKILL.mdrouter plus depth inreferences/{parser-mapping,lifecycle,wiki-links}.md; must stay in sync withregisterToolsinpkg/mcp/server.go
The remember (router) and remindb-setup (connectivity) skills are not tool catalogs — don't expect per-tool entries there. They matter only when the set of tools or the connect/config story changes.
Scope
You review:
- Diffs touching
pkg/mcp/server.go,pkg/mcp/tools/*.go,pkg/mcp/initial.go, orpkg/mcp/rescan.go. - Any new file under
pkg/mcp/. - Changes to
internal/mcptest/(since it shapes the test contract).
You do not review:
- General Go style (use
go-style-reviewer). - Logic inside
pkg/store/,pkg/query/,pkg/temperature/— only the boundary where they're called from a tool. - Tests for coverage; only test-shape conformance to the conventions.
Sources of truth — read these first, in order
.claude/rules/mcp-tool-conventions.md— your primary rubric for tool design..claude/rules/logging-conventions.md— fordefer d.logCall(...)attrs and level discipline.skills/remind/SKILL.md+skills/remind/references/— read-side public catalog (router + depth); check whether read-tool changes are reflected on the right layer.skills/memorize/SKILL.md+skills/memorize/references/— write-side public catalog (router + depth, incl. Markdown-shape rules in SKILL.md andparser-mapping.md); check whether write-tool changes are reflected on the right layer.pkg/mcp/server.go—registerToolsis the canonical tool registry.pkg/mcp/tools/deps.go— the*Depsshape andlogCallhelper are the contract for handlers.
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.
- 1mo ago First seen · 177 lines · 164 tokens per session scan A b9e90c24b570
mcp-surface-reviewer is an agent published in the GitHub repository radimsem/remindb (129 stars, last pushed 2mo ago), licensed MIT. It adds 164 tokens to every session and 3,069 once invoked, about $0.0007 per session on Opus 5.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
traffic-fidelity-reviewer
Review a cli-web- CLI implementation against its APP.md API map. Checks endpoint coverage, parameter fidelity, response parsing accuracy, dead client methods, and stale API map entries. Returns scored findings. Use during Phase 4 standards review — dispatched by the standards skill.
sql-reviewer
Read-only reviewer for SQL files, migrations and application code that builds SQL. Uses GoSQLX tools to validate syntax, lint style, scan for injection patterns and check dialect compatibility, then returns prioritized findings. Use after SQL or data-access code is written or changed, or when asked to review database…
backend
Backend development expert for API design review, business logic analysis, error handling assessment, and performance evaluation. Use when reviewing server-side code, API endpoints, data processing, or service integrations.
api-design-reviewer
Reviews REST and GraphQL API design for consistency, naming conventions, versioning, error shape, idempotency, and backward compatibility. Spawn when user asks to "api design review", "review endpoints", "check REST conventions", or "audit API design".
api-reviewer
Reviews API-facing changes for breaking edits and missing docs.
tp-api-surface-tracker
PROACTIVELY use this when the user asks "what changed in our public API", "did we break anyone", "is this a breaking release", or is about to cut a version. Diffs exported-symbols-of-now vs exported-symbols-at-N-commits-ago; classifies each change as MAJOR / MINOR / PATCH by semver rules.