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/ddr187/cursor-howto/code-reviewnpx skills add DDR187/cursor-howto --skill code-reviewgit clone --depth 1 https://github.com/DDR187/cursor-howtoWhat 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.00016 | $0.00954 |
| Opus 5 | $0.00008 | $0.00477 |
| Sonnet 5 | $0.00003 | $0.00191 |
| Haiku 4.5 | $0.00002 | $0.00095 |
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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Skill
Overview
Automatically review code and provide improvement suggestions, covering:
- Code quality analysis
- Security vulnerability detection
- Performance issue identification
- Best practice recommendations
Review Items
1. Code Quality
| Check Item | Description |
|---|---|
| Naming Conventions | Are variable, function, and class names clear |
| Code Structure | Does it follow single responsibility principle |
| Comment Completeness | Are key logic sections commented |
| Code Duplication | Is there duplicate code |
| Complexity | Are functions too complex |
2. Security Check
| Check Item | Description |
|---|---|
| SQL Injection | Is parameterized query used |
| XSS Vulnerability | Is output properly escaped |
| Sensitive Information | Are keys or credentials exposed |
| Input Validation | Is user input validated |
| Permission Check | Is permission verification performed |
3. Performance Check
| Check Item | Description |
|---|---|
| Loop Optimization | Are there unnecessary operations in loops |
| Memory Leaks | Are resources properly released |
| Async Handling | Is async used correctly |
| Cache Usage | Is caching used reasonably |
4. Best Practices
| Check Item | Description |
|---|---|
| Error Handling | Are errors handled properly |
| Type Safety | Are type definitions used |
| Test Coverage | Are there corresponding tests |
| Documentation Complete | Is necessary documentation present |
Execution Steps
-
Analyze Code Structure
- Identify file type
- Parse code structure
- Extract key information
-
Run Check Rules
- Apply quality rules
- Apply security rules
- Apply performance rules
-
Generate Report
- Summarize issues
- Categorize by severity
- Provide fix suggestions
Output Format
# Code Review Report
## Overview
- File: {filename}
- Review Time: {timestamp}
- Total Issues: {total_issues}
## Issue List
### 🔴 High ({high_count})
| Location | Issue | Suggestion |
|----------|-------|------------|
| {location} | {issue} | {suggestion} |
### 🟡 Medium ({medium_count})
| Location | Issue | Suggestion |
|----------|-------|------------|
| {location} | {issue} | {suggestion} |
### 🟢 Low ({low_count})
| Location | Issue | Suggestion |
|----------|-------|------------|
| {location} | {issue} | {suggestion} |
## Statistics
| Category | Count |
|----------|-------|
| Security Issues | {security_count} |
| Performance Issues | {performance_count} |
| Code Quality | {quality_count} |
| Best Practices | {practice_count} |
## Recommendations
{recommendations}
What ships with it
2 files 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 · 196 lines · 16 tokens per session scan A f4664b47c211
Code Review is a skill published in the GitHub repository DDR187/cursor-howto (2 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 954 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-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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…