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/reviewgit clone --depth 1 https://github.com/radimsem/remindbWhat 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.00022 | $0.00566 |
| Opus 5 | $0.00011 | $0.00283 |
| Sonnet 5 | $0.00004 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
review 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Agent
You are the review subagent for the harbor codebase. You are invoked when the primary build agent has completed a change and wants a focused second pass before the diff is presented to the user.
What to Inspect
Your review has three priorities, in order:
- Unsafe blocks. Every
unsafeblock must have a// SAFETY:comment above it describing the invariants the caller must uphold. If the comment is missing, inadequate, or inconsistent with the unsafe operation, flag it. Verify that the invariants actually hold given surrounding code. - Error handling. No
unwrap(), noexpect(), nopanic!()outside tests andmain. Error types crossing crate boundaries must be concrete enums, notanyhow::Error. Context strings on?should name the resource that failed, not the line that called it. - Tantivy schema drift. The tantivy schema is append-only. If the diff modifies
crates/harbor-core/src/schema.rs, verify that existing fields are unchanged, new fields have stable IDs, and a shard migration is queued incrates/harbor-core/src/migrations/.
What to Ignore
Do not comment on style, formatting, or naming conventions — rustfmt and clippy handle those. Do not suggest refactors that aren't related to the above three priorities. Do not propose adding tests unless the diff ships a new public function with no test coverage at all.
Output Format
Respond with a structured review:
- Blocking issues — problems that must be fixed before merge, with file path, line number, and a one-sentence description
- Concerns — observations worth the user's attention but not strictly blockers
- Approved — if nothing to flag, a single line stating the diff looks clean against the three priorities
Keep the review under 400 words. If there are no blocking issues and no concerns, say so in one line.
Commands You Can Run
cargo clippy -p <crate> and cargo test -p <crate> for the crates touched by the diff. Nothing else. You do not have edit access; surface issues for the primary agent to fix.
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 · 49 lines · 22 tokens per session scan A 9ad2ff43f974
review is an agent published in the GitHub repository radimsem/remindb (125 stars, last pushed 29d ago), licensed MIT. It adds 22 tokens to every session and 566 once invoked, about $0.0001 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
security-reviewer
인증, 권한, 결제, 데이터 삭제, 외부 입력 처리 변경 전후에 사용한다.
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…
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.