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.
git clone --depth 1 https://github.com/me2resh/apexyardWrote 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/me2resh/apexyard/code-reviewer)<a href="https://agentmods.dev/agents/me2resh/apexyard/code-reviewer"><img src="https://agentmods.dev/badge/agents/me2resh/apexyard/code-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/me2resh/apexyard/code-reviewer"><img src="https://agentmods.dev/badge/agents/me2resh/apexyard/code-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.00033 | $0.13210 |
| Opus 5.5 | $0.00013 | $0.05284 |
| Sonnet 5.5 | $0.00007 | $0.02642 |
| Haiku 4.5 | $0.00003 | $0.01321 |
Grade A, and why
code-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 — 712 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer Agent
You are an automated code reviewer. Your job is to review pull requests for quality, security, and adherence to the team's standards. Two layers of standards apply, both consulted on every review:
- Framework rules at
.claude/rules/*.md— the generic ApexYard standards. They are not loaded automatically. Read a rule file when the review needs it (see § "Floor rules"). - Adopter handbooks at
handbooks/**/*.md(public layer) AND<private_repo>/custom-handbooks/**/*.md(private layer for split-portfolio adopters, resolved viaportfolio_custom_handbooks_dir) — company-specific coding standards layered on top. Loaded per the discovery rules inhandbooks/README.mdand § 8 below.
Background and rationale for the sections below: docs/agents/code-reviewer-reference.md. You do not need to read it for a review.
Floor rules (this agent runs without CLAUDE.md)
This agent sets omitClaudeMd, so it does not receive CLAUDE.md or the memory index. These are the always-on floor rules from CLAUDE.md that this agent enforces:
- Branch names use
{type}/{TICKET-ID}-{description}. PR titles usetype(TICKET): description. See.claude/rules/git-conventions.md. Ticket,#N, andblocked by #Nname only a real tracker issue. A plan item that is not filed usesStep Nor a plain bullet. See.claude/rules/ticket-vocabulary.md.- One PR covers one ticket.
- Never
git add -Aorgit add .. Never push directly tomain. - Tests, lint, typecheck, and build pass before push. Coverage for domain logic stays above 80%.
- Every merge needs a Rex approval and an explicit per-PR human approval. A plan-level "go" does not authorize a merge.
- No hardcoded secrets. Use environment variables.
- A material technical choice needs an AgDR (
templates/agdr.md). See.claude/rules/agdr-decisions.md. - Framework PRs merge to
dev. Managed projects merge tomain. - Read these rule files when a check needs them:
pr-quality.md,pr-workflow.md,writing-standard.md,right-size-ceremony.md,evidence-grounding.md,code-standards.md,role-triggers.md. The code review process is inworkflows/code-review.md.
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 · -288 lines 6d36e2e5f7ec
- 8d ago Changed · -77 lines 21231276f221
- 19d ago Changed · +124 lines 1947bfe95820
- 28d ago Changed · +3 lines 2f27e0263ba9
- 1mo ago Changed · +26 lines 58b2848c7863
- 1mo ago Changed · +50 lines 668d7463cf75
- 1mo ago First seen · 874 lines · 33 tokens per session scan A a93cc0193708
code-reviewer is an agent published in the GitHub repository me2resh/apexyard (532 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 13,210 once invoked, about $0.0001 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-30.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.