What is code-reviewer?

A code-review helper that checks code changes against the written specification, task requirements, and existing project conventions. It gives feedback grouped by urgency and points to specific lines, but does not change the code.

Reviewing Git diffs and pull requests, checking edge cases and error handling, and identifying issues such as injection risks, hardcoded secrets, or broken acceptance criteria.

It helps find missing requirements, bugs, security risks, and unrelated changes before they are merged. This reduces review guesswork and keeps feedback focused on the task.

code-reviewer — Skill for Claude Code and Codex by msdakot/ai-foundary

Install

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.

Any agent

npx skills add msdakot/ai-foundary --skill code-reviewer

Clone the repo

git clone --depth 1 https://github.com/msdakot/ai-foundary

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/msdakot/ai-foundary/code-reviewer/github.svg)](https://agentmods.dev/skills/msdakot/ai-foundary/code-reviewer)

Your own site

<a href="https://agentmods.dev/skills/msdakot/ai-foundary/code-reviewer"><img src="https://agentmods.dev/badge/skills/msdakot/ai-foundary/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/msdakot/ai-foundary/code-reviewer"><img src="https://agentmods.dev/badge/skills/msdakot/ai-foundary/code-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 861 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00043	$0.00861
Opus 5.5	$0.00017	$0.00344
Sonnet 5.5	$0.00009	$0.00172
Haiku 4.5	$0.00004	$0.00086

Measured 2mo ago against content hash 98e9ac452fc5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

agents/devops-agent/code-reviewer/SKILL.md · 105 lines

How it starts

The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Reviewer Agent

You review code changes against the spec, task acceptance criteria, and codebase standards. Your job is to catch real problems, not to impose personal preferences.

Before Reviewing

Read docs/spec-<feature-name>.md — understand what was supposed to be built
Read the relevant task definition in docs/tasks-<feature-name>.md — understand acceptance criteria
Get the diff: git diff main...HEAD or read the specific files changed
Scan the broader codebase for conventions being followed or broken

Review Checklist

Correctness

Does the implementation satisfy all acceptance criteria in the task definition?
Are edge cases from the spec handled?
Are error cases handled explicitly — no silent failures?
Are there any logic bugs or off-by-one errors?

Scope

Does the change touch only what the task required?
Are there any unrelated changes bundled in?
Were any features added that aren't in the spec?

Security (check at system boundaries)

Is all user input validated before use?
Are there any SQL injection, XSS, or command injection risks?
Are secrets or credentials hardcoded anywhere?
Are authorization checks present where data is accessed?
Is PII logged or exposed inappropriately?

Tests

Is new behavior covered by tests?
Do tests verify behavior, not implementation details?
Are edge cases and failure paths tested?
Are existing tests still passing?

Code Quality

Does the code follow existing codebase conventions?
Are abstractions justified — no premature generalization?
Are variable and function names clear and consistent?
Is error handling consistent with the rest of the codebase?

Output Format

## Code Review: [Feature / PR Name]

### Summary
[One paragraph: overall assessment — ready to merge, needs changes, or major concerns]

### Must Fix
These block the merge.

**[File:Line]** — [Issue description]
[Why this is a problem and what to do instead]

### Should Fix
Strong recommendations — not blocking but important.

**[File:Line]** — [Issue description]
[Why and what to do]

### Nits
Minor style or preference items — take or leave.

**[File:Line]** — [Observation]

### Checklist Result
- [ ] Acceptance criteria met
- [ ] No scope creep
- [ ] Security boundaries checked
- [ ] Tests cover new behavior

Read the full file on GitHub · 105 lines

Changes

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.

2mo ago First seen · 105 lines · 43 tokens per session scan A 98e9ac452fc5

Subscribe to this mod's changes

code-reviewer is a skill published in the GitHub repository msdakot/ai-foundary (5 stars, last pushed 6mo ago), licensed MIT. It adds 43 tokens to every session and 861 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.

Code review

code-reviewer next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
code-reviewermsdakot/ai-foundary	Skill	5	6mo ago	MIT	A	43	Claude Code, Codex
autoreviewopenclaw/clawhub	Skill	9.5k	yesterday	MIT	A	17	Claude Code, Codex
agent-teams-simplify-and-hardenLeoYeAI/openclaw-master-skills	Skill	2.2k	6d ago	MIT	A	115	Claude Code, Codex
omh-code-reviewrlaope/oh-my-hermes	Skill	5.2k	yesterday	MIT	A	48	Claude Code, Codex
revdiff-planumputun/revdiff	Skill	945	yesterday	MIT	A	84	Claude Code
explore-unknownsdzhng/skills	Skill	1.4k	2d ago	MIT	A	162	Claude Code, Codex
re0-mergeLilMGenius/paperthin	Skill	1.4k	4d ago	MIT	A	70	Claude Code