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.
npx agentmods add skills/unrealandychan/clean-code-skill/code-reviewnpx skills add unrealandychan/clean-code-skill --skill code-reviewgit clone --depth 1 https://github.com/unrealandychan/clean-code-skillWhat 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 | $0.00000 | $0.00448 |
| Opus 5 | $0.00000 | $0.00224 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review & Quality Skill
Inspired by Addy Osmani's
agent-skills(addyosmani/agent-skills/skills/code-review-and-quality/SKILL.md).
Purpose
Perform rigorous, multi-dimensional code reviews across Correctness, Readability, Architecture, Security, and Performance.
When to Invoke This Skill
Trigger this skill when:
- The user requests a code review, pull request review, or quality check (
/code-review,/review-diff,/review-security,/review-perf). - Reviewing new code or refactoring changes before merging.
- Evaluating code health across the 5 axes of quality.
The 5-Axis Quality Framework
- Correctness: Spec/acceptance criteria alignment, edge cases, error handling, race conditions.
- Readability: Clear naming, small functions, self-documenting structure, why-focused comments.
- Architecture: Separation of concerns, bounded context boundaries, Ponytail anti-overengineering ladder.
- Security: OWASP top risks, input sanitization, secret protection, least privilege.
- Performance: Query batching, memory leak prevention, async efficiency, resource bounding.
Review Benchmark
Approve a change when it definitely improves overall code health, even if it isn't perfect. Perfect code doesn't exist — continuous improvement is the goal.
Quick Shortcuts
| Command | Action |
|---|---|
/code-review |
Full 5-axis code review on target files or git diff |
/review-diff |
Review git diff against HEAD / main branch |
/review-security |
Focused security audit (injection, secrets, OWASP) |
/review-perf |
Focused performance & memory leak audit |
/quality-gate |
Evaluate whether code passes merge readiness criteria |
Reference
- Canonical Rules:
skills/shared/code-review-quality-rules.md - Workflows & Prompts:
skills/code-review/WORKFLOWS.md
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.
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.
- 2d ago First seen · 55 lines · 0 tokens per session scan A 2d69661757a0
code-review is a skill published in the GitHub repository unrealandychan/clean-code-skill (6 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 448 tokens. 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.