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 instructions/jordanhubbard/ai-code-reviewer/agents-mdgit clone --depth 1 https://github.com/jordanhubbard/ai-code-reviewerWrote 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/instructions/jordanhubbard/ai-code-reviewer/agents-md)<a href="https://agentmods.dev/instructions/jordanhubbard/ai-code-reviewer/agents-md"><img src="https://agentmods.dev/badge/instructions/jordanhubbard/ai-code-reviewer/agents-md.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.01213 | $0.01213 |
| Opus 5 | $0.00607 | $0.00607 |
| Sonnet 5 | $0.00243 | $0.00243 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
ai-code-reviewer AGENTS.md 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Code Reviewer - Agent Instructions
This repository is an AI-powered code review and rewrite tool. The core design is data-driven:
- Agent behavior lives in
personas/<agent-name>/agent.yamlusing Oracle Agent Spec format. - Workflow behavior is configured in
config.yaml. - Build validation is configured with
source.build_command. - Rewrite acceptance belongs in
review.rewrite.contract, not hard-coded language, OS, or build-tool assumptions in the runner.
Quick Start
Validate an agent:
python3 persona_validator.py personas/security-hawk
Run the reviewer:
cp config.yaml.sample config.yaml
# Edit config.yaml: set source.root, source.build_command, review.workflow, review.persona
python3 reviewer.py --config config.yaml
Run forever mode:
python3 reviewer.py --config config.yaml --forever
Available Agents
Load agent configuration from personas/<agent-name>/agent.yaml.
| Agent | Focus | Use When |
|---|---|---|
freebsd-angry-ai |
Security, style(9), POSIX | FreeBSD-oriented production audits |
freebsd-rust-rewriter |
C/C++ to Rust, FreeBSD build integration | FreeBSD-specific rewrite persona |
security-hawk |
Vulnerabilities, exploits | Security audits and penetration-test style review |
performance-cop |
Speed, algorithms, cache | Performance optimization |
friendly-mentor |
Learning, best practices | Training, onboarding, open source |
example |
Balanced, educational | General code review |
Workflow Modes
review.workflow controls runner protocol and metadata files:
reviewusesREVIEW-INDEX.mdandREVIEW-SUMMARY.mdfor audits and fixes.rewriteusesREWRITE-INDEX.mdandREWRITE-SUMMARY.mdfor scoped source transformations such as refactors, API migrations, decomposition, simplification, hardening rewrites, or translations.
Personas provide project-specific taste and instructions. Do not add
language-specific rewrite policy to reviewer.py when the requirement can live
in the persona or review.rewrite.contract.
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 · 164 lines · 1,213 tokens per session scan A e0bb4a02f3d8
ai-code-reviewer AGENTS.md is an instructions file published in the GitHub repository jordanhubbard/ai-code-reviewer (44 stars, last pushed 3mo ago), licensed BSD-2-Clause. It adds 1,213 tokens to every session, about $0.0061 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).