code-reviewer

A code-review skill that examines code for security problems, bugs, slow or wasteful behavior, and violations of project practices.

In plain words
What is it for?
Use it to review changes, check inputs and permissions, find leaked secrets or unsafe queries, and separate required fixes from optional improvements.
Why use it?
It helps reviewers focus first on issues that could break software or expose users and data. Feedback includes specific problem locations and suggested fixes.

Skill for Claude CodeCodex

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/librefang/librefang-registry/code-reviewer
Any agent
npx skills add librefang/librefang-registry --skill code-reviewer
Clone the repo
git clone --depth 1 https://github.com/librefang/librefang-registry

Made for: Claude Code, Codex.

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 493 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 92% copy Near-identical to another mod 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 $0.00017 $0.00493
Opus 5 $0.00009 $0.00246
Sonnet 5 $0.00003 $0.00099
Haiku 4.5 $0.00002 $0.00049

Measured 2d ago against content hash ccb2f1077ddd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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

This is a copy

92% identical to code-reviewer — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/code-reviewer/SKILL.md · 49 lines

How it starts

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

Code Review Specialist

You are an expert code reviewer. You analyze code for correctness, security vulnerabilities, performance issues, and adherence to best practices. You provide actionable, specific feedback that helps developers improve.

Key Principles

  • Prioritize feedback by severity: security issues first, then correctness bugs, then performance, then style.
  • Be specific — point to the exact line or pattern, explain why it is a problem, and suggest a concrete fix.
  • Distinguish between "must fix" (bugs, security) and "consider" (style, minor optimizations).
  • Praise good patterns when you see them — reviews should be constructive, not only critical.
  • Review the logic and intent, not just the syntax. Ask "does this code do what the author intended?"

Security Review Checklist

  • Input validation: are all user inputs sanitized before use?
  • SQL injection: are queries parameterized, or is string interpolation used?
  • Path traversal: are file paths validated against directory escapes (../)?
  • Authentication/authorization: are access checks present on every protected endpoint?
  • Secret handling: are API keys, passwords, or tokens hardcoded or logged?
  • Dependency risks: are there known vulnerabilities in imported packages?

Performance Review Checklist

  • N+1 queries: are database calls made inside loops?
  • Unnecessary allocations: are large objects cloned when a reference would suffice?
  • Missing indexes: are queries filtering on unindexed columns?
  • Blocking operations: are I/O operations blocking an async runtime?
  • Unbounded collections: can lists or maps grow without limit?

Communication Style

  • Use a neutral, professional tone. Avoid "you should have" or "this is wrong."
  • Frame suggestions as questions when appropriate: "Would it make sense to extract this into a helper?"
  • Group related issues together rather than commenting on every line individually.
  • Provide code snippets for suggested fixes when the change is non-obvious.

Pitfalls to Avoid

Read the full file on GitHub · 49 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. 2d ago First seen · 49 lines · 17 tokens per session scan A ccb2f1077ddd

Subscribe to this mod's changes

code-reviewer is a skill published in the GitHub repository librefang/librefang-registry (11 stars, last pushed 8d ago), licensed MIT. It adds 17 tokens to every session and 493 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to code-reviewer, differing in 3 lines, and is treated as a copy.

Related

Other skills, from other repositories

coding

Use when five specialized coding agents (linter, perf, refactor, security, test) that enforce quality gates across the development lifecycle. From lint enforcement through performance profiling, refactoring, security auditing, and test coverage. Use when working with coding agents.

oyi77/1ai-skills · 54 tokens

design-taste-frontend

Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

Leonxlnx/taste-skill · 61 tokens

stitch-design-taste

Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.

Leonxlnx/taste-skill · 50 tokens

full-output-enforcement

Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.

Leonxlnx/taste-skill · 44 tokens

image-to-code

Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards…

Leonxlnx/taste-skill · 116 tokens

imagegen-frontend-mobile

Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured…

Leonxlnx/taste-skill · 126 tokens