A structured method for examining code changes for correctness, security, speed, and long-term maintainability.

Use it for pull requests, proposed changes, pre-commit checks, security reviews, and finding opportunities to simplify or improve code.

It gives reviews a consistent process, so important risks and unexpected changes are less likely to be missed.

code-review — Skill for Claude Code and Codex by FreePeak/ktme

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 FreePeak/ktme --skill code-review

Clone the repo

git clone --depth 1 https://github.com/FreePeak/ktme

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/freepeak/ktme/code-review/github.svg)](https://agentmods.dev/skills/freepeak/ktme/code-review)

Your own site

<a href="https://agentmods.dev/skills/freepeak/ktme/code-review"><img src="https://agentmods.dev/badge/skills/freepeak/ktme/code-review/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/freepeak/ktme/code-review"><img src="https://agentmods.dev/badge/skills/freepeak/ktme/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,879 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.00020	$0.02879
Opus 5.5	$0.00008	$0.01152
Sonnet 5.5	$0.00004	$0.00576
Haiku 4.5	$0.00002	$0.00288

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

Security

Grade A, and why

code-review 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.

.kilo/skills/code-review/SKILL.md · 503 lines

How it starts

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

Code Review

A systematic approach to reviewing code changes with focus on quality, security, performance, and maintainability.

When to Use

Use this skill when:

Reviewing pull requests
Evaluating proposed changes
Conducting pre-commit reviews
Performing security audits
Analyzing code for refactoring opportunities

Review Framework

Phase 1: Understand Context

Goal: Understand what changed and why

Steps:

Read PR description or commit message
Identify related issues/tickets
Understand the business requirement
Note the scope of changes

Context Checklist:

CONTEXT:
- Issue/PR: [link or number]
- Author: [who made the changes]
- Scope: [files/directories affected]
- Purpose: [what problem it solves]
- Dependencies: [any related PRs or changes]

Questions to Answer:

What problem does this solve?
Is this the right approach?
Are there alternative solutions?
What's the impact on existing code?

Phase 2: Review the Diff

Goal: Examine actual code changes

Steps:

Review files changed (start with most important)
Check for unexpected changes
Examine each diff hunk carefully
Note questions and concerns

Diff Review Template:

## Files Changed

### Critical Files
- `file1:line` - [concern or observation]
- `file2:line` - [concern or observation]

### Supporting Files
- `file3:line` - [concern or observation]

### Test Files
- `test_file:line` - [concern or observation]

## Observations
1. [observation with file:line reference]
2. [observation with file:line reference]

Phase 3: Quality Checks

Categories to Evaluate:

3.1 Correctness

CORRECTNESS:
- [ ] Logic is correct
- [ ] Handles edge cases
- [ ] Error handling is appropriate
- [ ] No off-by-one errors
- [ ] Null/None handling is proper
- [ ] Type conversions are safe

ISSUES:
- `file:line` - [description of issue]

3.2 Security

SECURITY:
- [ ] No SQL injection vulnerabilities
- [ ] Input validation is proper
- [ ] No hardcoded secrets
- [ ] Authentication/authorization checked
- [ ] No XSS vulnerabilities (if web)
- [ ] Sensitive data is protected
- [ ] Rate limiting considered
- [ ] Dependencies are safe

ISSUES:
- `file:line` - [description of security concern]

Read the full file on GitHub · 503 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 · 503 lines · 20 tokens per session scan A 1b66558d12a6

Subscribe to this mod's changes

code-review is a skill published in the GitHub repository FreePeak/ktme (15 stars, last pushed 8mo ago), licensed MIT. It adds 20 tokens to every session and 2,879 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.

Code review

code-review next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
code-reviewFreePeak/ktme	Skill	15	8mo ago	MIT	A	20	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	2d ago	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