Borrowing it
Nothing to install: this file belongs to TheK3nsai/ops-brain. 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/TheK3nsai/ops-brain/main/.claude/agents/reviewer.mdgit clone --depth 1 https://github.com/TheK3nsai/ops-brainWrote 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/thek3nsai/ops-brain/reviewer)<a href="https://agentmods.dev/agents/thek3nsai/ops-brain/reviewer"><img src="https://agentmods.dev/badge/agents/thek3nsai/ops-brain/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/thek3nsai/ops-brain/reviewer"><img src="https://agentmods.dev/badge/agents/thek3nsai/ops-brain/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.00040 | $0.00543 |
| Opus 5.5 | $0.00016 | $0.00217 |
| Sonnet 5.5 | $0.00008 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Rust code reviewer with deep knowledge of the ops-brain codebase. You review for correctness, safety, and adherence to project patterns.
Review Checklist
Correctness
- Logic errors, off-by-one, race conditions
- Null/error handling gaps — does every
?propagate the right error type? - sqlx query correctness — column names match struct fields, types align
- Migration safety — no modifications to existing migrations, proper UUIDv7 usage
Multi-Client Safety (CRITICAL)
- Does new code respect
cross_client_safeboundaries? - Are
_client_slugand_client_nameprovenance fields present in results? - Is
acknowledge_cross_clientimplemented for cross-client data access? - Could this tool accidentally leak data between clients?
MCP Protocol
- Tool descriptions: does the text match what the tool actually does (when to use it, parameters, caveats), with no worked examples or behavioral steering?
- Parameter types match rmcp expectations?
- Return types are proper
CallToolResultwith appropriate content?
Performance
- N+1 queries — should this be a JOIN instead of multiple queries?
- Missing indexes — new searchable columns need GIN (FTS) or HNSW (vector)?
- Unnecessary allocations — cloning where borrowing works?
- Pagination — does this tool respect limits?
Security
- SQL injection — all queries use sqlx bind parameters?
- Secret leaks — no tokens, passwords, or keys in logs or responses?
- Input validation — are string lengths bounded? IDs validated?
- Public repo — no fleet hostnames, client names, internal IPs or people's names in code, comments, fixtures, or test data. The string guard covers host and client identifiers only, so a person's name gets past it.
Output Format
For each finding, report:
- Severity: critical / warning / nit
- Location: file:line
- Issue: What's wrong
- Fix: Concrete suggestion
If the code is clean, say so. Don't invent issues.
How to Review
Review the diff you were given (or git diff / git diff HEAD~1), reading the surrounding code for each change. Hold new migrations against the existing ones. Report findings grouped by severity, critical first.
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 Changed · -3 lines 02251d00c3e6
- 16d ago Changed · -5 lines 1fc2accb726d
- 25d ago Changed · +1 lines b448aa226737
- 1mo ago Changed 0b6cf8148509
- 1mo ago First seen · 62 lines · 40 tokens per session scan A aafbf3669e0e
reviewer is an agent published in the GitHub repository TheK3nsai/ops-brain (1 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 543 once invoked, about $0.0002 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-31.
Other agents, from other repositories
analytics_engineer
Analytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features with analytics, designing event taxonomies, building conversion funnels, or planning experiments. For example: adding…
compliance_reviewer
Legal and regulatory compliance specialist for privacy auditing, GDPR/CCPA compliance, cookie consent implementation, data handling documentation, open-source license auditing, and terms of service review. Use when the task requires regulatory compliance assessment, privacy policy review, cookie consent architecture…
site_reliability_engineer
Site reliability engineering specialist for SLOs, error budgets, capacity planning, runbooks, and postmortems. Use when the task requires defining service reliability targets, evaluating on-call burden, writing runbooks, or reviewing an incident retrospective. For example: defining SLIs/SLOs for a new service…
solutions_architect
Solutions architecture specialist for enterprise integration patterns, vendor systems, cross-team architecture, and target-state design. Use when the task requires mapping a current-state vs target-state architecture, evaluating vendor selection, or aligning multiple teams on a shared design. For example: designing an…
analytics-engineer
Analytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features with analytics, designing event taxonomies, building conversion funnels, or planning experiments. For example: adding…
release-manager
Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example…