A combined code and interface review tool for a working directory, Git changes, or selected files. It checks engineering issues and, for interface files, also checks visual quality.

Use it to review a pull request, inspect a diff before submission, or run a review check in continuous integration.

It puts code checks and interface checks into one report, including unfinished markers, loose types, large files, and design problems.

review — Skill for Claude Code and Codex by Dragoon0x

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 Dragoon0x/dragoon-skills --skill review

Clone the repo

git clone --depth 1 https://github.com/Dragoon0x/dragoon-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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/dragoon0x/dragoon-skills/review/github.svg)](https://agentmods.dev/skills/dragoon0x/dragoon-skills/review)

Your own site

<a href="https://agentmods.dev/skills/dragoon0x/dragoon-skills/review"><img src="https://agentmods.dev/badge/skills/dragoon0x/dragoon-skills/review/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/dragoon0x/dragoon-skills/review"><img src="https://agentmods.dev/badge/skills/dragoon0x/dragoon-skills/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 131 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 644 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.

Model	Per session	Once invoked
Fable 5.1	$0.00131	$0.00644
Opus 5	$0.00066	$0.00322
Sonnet 5	$0.00026	$0.00129
Haiku 4.5	$0.00013	$0.00064

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

Security

Grade A, and why

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 10d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/review.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/review/SKILL.md · 67 lines

What it actually says

/review

Unified review. The integration that no other skill pack ships.

When you run /review on a diff, it scans every file:

runs slop detection (all 12 rules)
runs lightweight engineering checks (TODO/FIXME, any types, large files)
if any UI files are present, automatically runs /critique on the project

One report. Both lanes. The thing teams actually need.

When to use

Run /review when:

The user wants to review a PR or diff
Before opening a pull request
The user says "review my changes", "look at this diff", "audit this branch"
As a CI step on every PR

Run it

# review the working directory
node ~/.claude/skills/dragoon/skills/review/scripts/review.js

# review only changed files in git
node ~/.claude/skills/dragoon/skills/review/scripts/review.js --diff

# review a specific file or folder
node ~/.claude/skills/dragoon/skills/review/scripts/review.js src/Card.tsx

# CI gate: fail if design score < 80 or any high-severity findings
node ~/.claude/skills/dragoon/skills/review/scripts/review.js --diff --threshold 80

Flags:

--diff only review files in git diff (uses git diff --name-only HEAD)
--manifest <p> use a specific manifest
--json machine-readable
--threshold <n> CI gate
--no-design skip design critique (slop only)
--no-slop skip slop (critique only)
--help full usage

Exit codes

0 clean (or threshold met)
1 high-severity findings, or threshold not met
2 bad usage

What's checked

Engineering signals:

eng-001 unresolved TODO / FIXME / HACK / XXX markers
eng-002 use of any type in TypeScript
eng-003 files over 600 lines

Design signals: all 12 slop rules. See node ~/.claude/skills/dragoon/skills/slop/scripts/slop.js --rules.

Design quality: full /critique scoring on the project's manifest.

Files

What ships with it

1 file 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.

scripts/review.js 7.9 KB runs 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.

10d ago First seen · 67 lines · 131 tokens per session scan A 62f7c888e823

Subscribe to this mod's changes

review is a skill published in the GitHub repository Dragoon0x/dragoon-skills (4 stars, last pushed 4mo ago), licensed MIT. It adds 131 tokens to every session and 644 once invoked, about $0.0007 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.

Claude Code Code review Design and UX accessibility agent-skills contrast-checker dark-mode design-tokens

ss-learn

Capture a human-approved UI design lesson as a privacy-minimized local StyleSeed candidate, review it, and prepare an opt-in share package without transmitting project code, prompts, screenshots, or brand data. Use when a person asks StyleSeed to remember, learn from, generalize, review, or prepare a reusable rule…

bitjaru/styleseed · 73 tokens

ss-lint

Quick automated lint — detects common design system violations in seconds.

bitjaru/styleseed · 15 tokens

ss-review

Review UI code for design system compliance, accessibility, and best practices.

bitjaru/styleseed · 16 tokens

design-system-tokens

Design token management with the W3C Design Token spec, three-tier hierarchy (global/alias/component), OKLCH color, Style Dictionary transforms, and dark mode theming. Use when creating token files, implementing theme systems, or building design-to-code pipelines.

yonatangross/orchestkit · 58 tokens

figma-extract-design-system

Extract a design system from vibe-coded production apps that never had one: inventory components, mine de-facto styling into DTCG tokens, scaffold a Storybook package, port components, and optionally round-trip tokens/components into Figma. Use when the user wants to 'extract a design system', 'create a design system…

southleft/figma-console-mcp-skills · 133 tokens

figma-version-history

List a Figma file's version history, snapshot the file at any past version, and diff two versions (added/removed/renamed pages plus deep per-component changes). Use when the user wants to inspect Figma history — triggers: 'list Figma versions', 'what versions does this file have', 'show version history', 'snapshot…

southleft/figma-console-mcp-skills · 181 tokens