agentmods.dev

code-review

code-review is a skill for Claude Code from lucastamoios/skills. It costs 65 tokens per session (2,145 once invoked), scanned A, original, MIT.

A structured review of a pull request or code difference, checking for bugs, security problems, edge cases, weak tests, and missed requirements.

In plain words
What is it for?
Use it to review a GitHub pull request, the current uncommitted changes, or differences between branches, including related imports, dependencies, history, and project-specific lessons.
Why use it?
It helps find problems before changed code is merged. Each finding explains what is wrong and what action to take, while uncertain findings are marked as such.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

not rated 2repo 3mo ago A scan 65 tokens original MIT

Good fit Use it to review a GitHub pull request, the current uncommitted changes…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lucastamoios/skills/code-review
View source ↗ lucastamoios/skills
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 lucastamoios/skills --skill code-review
Clone the repo
git clone --depth 1 https://github.com/lucastamoios/skills

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/lucastamoios/skills/code-review.svg)](https://agentmods.dev/skills/lucastamoios/skills/code-review)
Your own site
<a href="https://agentmods.dev/skills/lucastamoios/skills/code-review"><img src="https://agentmods.dev/badge/skills/lucastamoios/skills/code-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,145 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00065 $0.02145
Opus 5 $0.00032 $0.01073
Sonnet 5 $0.00013 $0.00429
Haiku 4.5 $0.00006 $0.00215

Measured 6d ago against content hash 7614dd5873e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 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.

code-review/SKILL.md · 150 lines

How it starts

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

Code Review

This skill reviews a PR or diff for bugs, logic errors, security vulnerabilities, edge cases, test quality, and alignment with requirements. It uses an agentic approach: dynamically investigate suspicious patterns, follow imports, check git history, and trace dependencies. After the investigation, it runs through a checklist to ensure nothing was missed.

The output is actionable: every finding tells the coding agent (or human) exactly what is wrong and what to do about it. If you are not sure about a finding, say so explicitly in the comment.

Argument: $ARGUMENTS

Step 1: Load context

  1. Identify the PR or diff. If $ARGUMENTS is a PR number, run gh pr view $ARGUMENTS --json baseRefName,headRefName,title,body and gh pr diff $ARGUMENTS. If it is "current" or empty, use git diff against the base branch. If it is a branch name, diff against main.

  2. Read the changed files list. Run git diff <base>..HEAD --name-only to understand the scope.

  3. Load project learnings. Check if docs/codebase-learnings.json exists (or a similar path). If it does, filter learnings by tags relevant to the changed files. For example, if the diff touches models or querysets, load learnings tagged with orm, multi_tenancy, security, permissions. Use jq to filter:

    cat docs/codebase-learnings.json | jq '[.[] | select(.tags | any(. == "security" or . == "orm" or . == "multi_tenancy"))]'

    Determine the relevant tags from the changed file paths:

    • Models, querysets, managers -> orm, multi_tenancy, security, permissions
    • Views, API endpoints -> api_design, permissions, security
    • Services -> architecture, error_handling
    • Tests -> test_patterns
    • Celery tasks -> celery_async
    • Migrations -> database
    • Templates, static files -> code_style
    • Performance-sensitive paths -> performance

Read the full file on GitHub · 150 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.

  1. 6d ago First seen · 150 lines · 65 tokens per session scan A 7614dd5873e1

Subscribe to this mod's changes

code-review is a skill published in the GitHub repository lucastamoios/skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 65 tokens to every session and 2,145 once invoked, about $0.0003 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-31.

Code review
Related

Other skills, from other repositories

autoreview

Pre-commit/ship code review: Codex default; optional Claude or Pi.

openclaw/clawhub · 20 tokens

rework-rate

Measure and interpret PR rework rate — the emerging 5th DORA metric.

bradygaster/squad · 20 tokens

omh-code-review

This is a Hermes-native code-review workflow skill.

rlaope/oh-my-hermes · 46 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

code-reviewer

Code review specialist focused on patterns, bugs, security, and performance.

RightNow-AI/openfang · 17 tokens

full-repo-review

Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.

notque/vexjoy-agent · 22 tokens