code-review

A structured prompt for reviewing code in a chosen programming language and focus area. It asks for issues, improvement suggestions, strengths, and the code’s behavior.

In plain words
What is it for?
Use it to review a code sample and organize findings into problems, suggestions, and things done well.
Why use it?
It gives reviews a consistent structure and directs attention to bugs, security, performance, and other selected concerns.

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

Made for: Claude Code, Codex.

Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 93 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 $0.00012 $0.00093
Opus 5 $0.00006 $0.00046
Sonnet 5 $0.00002 $0.00019
Haiku 4.5 $0.00001 $0.00009

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

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/registry/items/code-review/SKILL.md · 23 lines

What it actually says

Code Review

Review the following {{language}} code. Focus on {{focus_area}}.

Provide feedback organized as:

  1. Issues found (bugs, security, performance)
  2. Suggestions for improvement
  3. What the code does well
{{code}}
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. yesterday First seen · 23 lines · 12 tokens per session scan A b756c31f0a33

Subscribe to this mod's changes

code-review is a skill published in the GitHub repository gridctl/gridctl (45 stars, last pushed 2d ago), licensed Apache-2.0. It adds 12 tokens to every session and 93 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.