review-example

review-example is a skill for Claude Code, Codex from DGouron/review-flow. It costs 21 tokens per session (342 once invoked), scanned A, original, MIT.

An example checklist and report format for reviewing code changes. It covers readability, architecture, tests, error handling, and common security risks.

In plain words
What is it for?
Use it for ordinary code reviews, especially when checking new tests, naming, duplicated code, dependency handling, hardcoded secrets, SQL injection, or cross-site scripting. The review is reported as a summary, blocking issues, suggestions, and positive points.
Why use it?
It gives reviewers a consistent way to find important defects and explain why they matter, rather than relying on an unstructured opinion.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

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.

agentmods
npx agentmods add skills/dgouron/review-flow/review-example
Any agent
npx skills add DGouron/review-flow --skill review-example
Clone the repo
git clone --depth 1 https://github.com/DGouron/review-flow

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.

agentmods badge for review-example

README.md
[![agentmods](https://agentmods.dev/badge/skills/dgouron/review-flow/review-example.svg)](https://agentmods.dev/skills/dgouron/review-flow/review-example)
Your own site
<a href="https://agentmods.dev/skills/dgouron/review-flow/review-example"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/review-example.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 342 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.00342
Opus 5 $0.00010 $0.00171
Sonnet 5 $0.00004 $0.00068
Haiku 4.5 $0.00002 $0.00034

Measured 6d ago against content hash e21376d968f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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

examples/skills/review-example/SKILL.md · 67 lines

What it actually says

Code Review Example

Context

You are: A code reviewer focused on quality and best practices.

Your approach:

  • Direct and factual feedback
  • Focus on maintainability and readability
  • Explain the "why" before the "how"

Review Checklist

Code Quality

  • Code follows project conventions
  • No code duplication
  • Clear naming (variables, functions, classes)
  • Appropriate error handling

Architecture

  • Single Responsibility Principle respected
  • Dependencies are properly injected
  • No circular dependencies

Testing

  • New code has tests
  • Tests are meaningful and not just coverage padding
  • Edge cases are covered

Security

  • No hardcoded secrets
  • Input validation where needed
  • No SQL injection or XSS vulnerabilities

Output Format

Generate a markdown report with:

  1. Summary: Overall assessment (1-2 sentences)
  2. Blocking Issues: Must fix before merge
  3. Suggestions: Nice to have improvements
  4. Positive Points: What was done well

Example Output

# Code Review - MR #123

## Summary
Solid implementation with minor improvements needed.

## Blocking Issues
- Missing error handling in `fetchUser()` - uncaught promise rejection

## Suggestions
- Consider extracting the validation logic to a separate function

## Positive Points
- Good test coverage
- Clear variable naming
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.

  1. 6d ago First seen · 67 lines · 21 tokens per session scan A e21376d968f6

Subscribe to this mod's changes

review-example is a skill published in the GitHub repository DGouron/review-flow (42 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 342 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.

Related

Other skills, from other repositories

issue

Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…

jeremylongshore/tons-of-skills-marketplace · 115 tokens

swarm-pr-review

Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…

ZaxbyHub/opencode-swarm · 91 tokens

brooks-sweep

Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…

hyhmrright/brooks-lint · 178 tokens

include-test-files-that-assert-on-behavior-being-changed-in-decl

When delegating a task affected by this skill, include.

ZaxbyHub/opencode-swarm · 29 tokens

address-review

Read PR review comments from GitHub, evaluate, address, and reply.

fpindej/netrock · 14 tokens

request-review

Dispatch a fresh reviewer agent with a clean context to critique the code after audit-code passes. The reviewer has no shared state with the coding agent and gives a genuine second opinion. Use after audit-code passes, before committing, or when user wants an independent code review.

danielvm-git/bigpowers · 56 tokens