code-review-expert

code-review-expert is a skill for Claude Code, Codex from sanyuan0704/sanyuan-skills. It costs 32 tokens per session (1,273 once invoked), scanned A, original, MIT.

A structured review of the code currently changed in Git, the system used to track code revisions. It checks design quality, security risks, and possible improvements.

In plain words
What is it for?
Use it to review a branch or set of Git changes and receive prioritized, actionable feedback.
Why use it?
It helps find serious bugs, security problems, and maintainability issues before the changes are merged.

Skill for Claude CodeCodex

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

not rated 3.9krepo +8 4mo ago A scan Socket: passSnyk: passSkillSpector: pass 32 tokens original MIT

Good fit Use it to review a branch or set of Git changes and receive prioritized, actionable feedback.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sanyuan0704/sanyuan-skills/code-review-expert
About the project

sanyuan-skills is a collection of reusable instructions, called agent skills, that extend Claude Code and other AI coding terminals with defined workflows. Developers use it for code review, learning, skill quality checks, skill creation, and organizing knowledge into wikis or study materials. The catalogue entries are individual skills from this collection.

sanyuan0704/sanyuan-skills · 3,904 stars · on GitHub

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 sanyuan0704/sanyuan-skills --skill code-review-expert
Clone the repo
git clone --depth 1 https://github.com/sanyuan0704/sanyuan-skills

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/sanyuan0704/sanyuan-skills/code-review-expert/github.svg)](https://agentmods.dev/skills/sanyuan0704/sanyuan-skills/code-review-expert)
Your own site
<a href="https://agentmods.dev/skills/sanyuan0704/sanyuan-skills/code-review-expert"><img src="https://agentmods.dev/badge/skills/sanyuan0704/sanyuan-skills/code-review-expert/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.

agentmods 80×15 button for code-review-expert

Your own site · 80×15
<a href="https://agentmods.dev/skills/sanyuan0704/sanyuan-skills/code-review-expert"><img src="https://agentmods.dev/badge/skills/sanyuan0704/sanyuan-skills/code-review-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,273 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. Third-party audits
  • Socket pass 18 Mar 2026
  • Snyk pass 2 Mar 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00032 $0.01273
Opus 5 $0.00016 $0.00636
Sonnet 5 $0.00006 $0.00255
Haiku 4.5 $0.00003 $0.00127

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

Security

Grade A, and why

code-review-expert 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 11d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/code-review-expert/SKILL.md · 157 lines

How it starts

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

Code Review Expert

Overview

Perform a structured review of the current git changes with focus on SOLID, architecture, removal candidates, and security risks. Default to review-only output unless the user asks to implement changes.

Severity Levels

Level Name Description Action
P0 Critical Security vulnerability, data loss risk, correctness bug Must block merge
P1 High Logic error, significant SOLID violation, performance regression Should fix before merge
P2 Medium Code smell, maintainability concern, minor SOLID violation Fix in this PR or create follow-up
P3 Low Style, naming, minor suggestion Optional improvement

Workflow

1) Preflight context

  • Use git status -sb, git diff --stat, and git diff to scope changes.
  • If needed, use rg or grep to find related modules, usages, and contracts.
  • Identify entry points, ownership boundaries, and critical paths (auth, payments, data writes, network).

Edge cases:

  • No changes: If git diff is empty, inform user and ask if they want to review staged changes or a specific commit range.
  • Large diff (>500 lines): Summarize by file first, then review in batches by module/feature area.
  • Mixed concerns: Group findings by logical feature, not just file order.

2) SOLID + architecture smells

  • Load references/solid-checklist.md for specific prompts.
  • Look for:
    • SRP: Overloaded modules with unrelated responsibilities.
    • OCP: Frequent edits to add behavior instead of extension points.
    • LSP: Subclasses that break expectations or require type checks.
    • ISP: Wide interfaces with unused methods.
    • DIP: High-level logic tied to low-level implementations.
  • When you propose a refactor, explain why it improves cohesion/coupling and outline a minimal, safe split.
  • If refactor is non-trivial, propose an incremental plan instead of a large rewrite.

Read the full file on GitHub · 157 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 11d ago First seen · 157 lines · 32 tokens per session scan A 976a50590858

Subscribe to this mod's changes

code-review-expert is a skill published in the GitHub repository sanyuan0704/sanyuan-skills (3,904 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 1,273 once invoked, about $0.0002 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.