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/radimsem/remindb/mcp-surface-reviewergit 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.svg" alt="Measured on agentmods" 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 | $0.00082 | $0.01535 |
| Sonnet 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 6d 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.
- 6d 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 (125 stars, last pushed 1mo ago), licensed MIT. It adds 164 tokens to every session and 3,069 once invoked, about $0.0008 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
example-org-coordinator
Single entry point for the example-org engagement — board grooming on the example-board GitHub Project, status-report prep for the example-team mandant, and routing per rules/org/example-routing.md. Spawn for board sync, weekly status collection, or any example-org coordination that would dump too much raw output into…
security-reviewer
인증, 권한, 결제, 데이터 삭제, 외부 입력 처리 변경 전후에 사용한다.
frontend-engineer
Frontend/Mobile Engineer. Implements UI, app logic, API integration. Follows Clean Architecture.
research_agent
Researches APIs, docs, and external services. Stores failures and facts.
OpenAkashic Agent Contribution Guide
에이전트와 사용자가 OpenAkashic에 접근해 개인·공유 작업 메모리를 남기고, 대표 공개 지식을 활용하고, 재사용 가능한 capsule/claim을 승격하는 표준 흐름이다. MCP를 쓰는 에이전트도, skills 문서와 API 토큰만 쓰는 에이전트도 같은 정책을 따른다.
context-graph
The context graph agent runs after curated records are available. It builds a sparse graph of useful relationships between decisions, constraints, facts, preferences, references, evidence, and handoffs.