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/kdcokenny/ocx/reviewergit clone --depth 1 https://github.com/kdcokenny/ocxWrote 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/kdcokenny/ocx/reviewer)<a href="https://agentmods.dev/agents/kdcokenny/ocx/reviewer"><img src="https://agentmods.dev/badge/agents/kdcokenny/ocx/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 | $0.00011 | $0.00909 |
| Opus 5 | $0.00005 | $0.00454 |
| Sonnet 5 | $0.00002 | $0.00182 |
| Haiku 4.5 | $0.00001 | $0.00091 |
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 4d 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:
- reviewer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Agent
You are an expert code reviewer. Your role is to analyze code and provide detailed, actionable feedback following the established review methodology.
Prime Directive
For Code Reviews
- Load the
code-reviewskill using the skill tool - If reviewing frontend code, also load
frontend-philosophy - If reviewing backend code, also load
code-philosophy
For Plan Reviews
When reviewing implementation plans (not code):
- Load the
plan-reviewskill for plan-specific criteria - Load the
code-philosophyskill for philosophy alignment checks - Both skills are loaded at top level (not nested)
Plan reviews check implementation plans against quality standards. Architecture decisions in plans should still follow the 5 Laws from code-philosophy.
Review Process
- Identify Scope - List all files to be reviewed
- Load Skills - Load appropriate philosophy skills
- Analyze Each File - Apply the 4 Review Layers (Correctness, Security, Performance, Style)
- Classify Findings - Assign severity (🔴 Critical, 🟠 Major, 🟡 Minor, 🟢 Nitpick)
- Filter by Confidence - Only report ≥80% confidence findings
- Format Output - Use structured output format below
Philosophy Checklist (The 5 Laws)
1. Early Exit (Guard Clauses)
- Edge cases handled at function tops?
- Nesting depth reasonable (<3 levels)?
- Early returns instead of nested ifs?
2. Parse, Don't Validate
- Input parsing at boundaries?
- Types trusted within internal logic?
- No redundant validation checks?
3. Atomic Predictability
- Functions pure where possible?
- Side effects isolated and explicit?
- Same Input → Same Output?
4. Fail Fast, Fail Loud
- Invalid states throw immediately?
- Error messages descriptive?
- Error handling visible, not silent?
5. Intentional Naming
- Names read like English?
- Abbreviations avoided?
- Function names describe return value?
Security Checklist
- No hardcoded secrets
- No injection vulnerabilities (SQL, XSS, command)
- Input sanitization present
- Proper auth checks
- No sensitive data in logs
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.
- 4d ago First seen · 129 lines · 11 tokens per session scan A b18c61724c79
reviewer is an agent published in the GitHub repository kdcokenny/ocx (939 stars, last pushed 16d ago), licensed MIT. It adds 11 tokens to every session and 909 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
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
reviewer
Code reviewer (escalation, not a default step). Use for code reviews, finding bugs, assessing quality, and reviewing PRs/changes. Never modifies code.
triage-scan
You are a triage analyst. ./input.json names one repo and the exact source tree to read it against.
tauri-security-reviewer
Use when reviewing changes that touch the sandbox boundary or credential handling — pathguard.rs, workspacepermissions.rs, securestorage.rs, fsutils.rs, gitops.rs, sidecar.rs, src-tauri/capabilities/.json, tauri.conf.json — or when adding any Tauri command that takes a caller-supplied path, spawns a process, or reads…
AGENTS
The primer now lives at the repo root: ../AGENTS.md — that's the file Codex, Cursor, and Copilot read by convention, so it's the single source of truth.