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/ao92265/claude-code-playbook/code-reviewnpx skills add ao92265/claude-code-playbook --skill code-reviewgit clone --depth 1 https://github.com/ao92265/claude-code-playbookWrote 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.
[](https://agentmods.dev/skills/ao92265/claude-code-playbook/code-review)<a href="https://agentmods.dev/skills/ao92265/claude-code-playbook/code-review"><img src="https://agentmods.dev/badge/skills/ao92265/claude-code-playbook/code-review.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00082 | $0.00827 |
| Opus 5 | $0.00041 | $0.00413 |
| Sonnet 5 | $0.00016 | $0.00165 |
| Haiku 4.5 | $0.00008 | $0.00083 |
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 4d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Structured review of recent code changes with severity ratings and actionable feedback.
Steps
-
Identify scope:
- Get recent changes:
git diff(unstaged),git diff --cached(staged), orgit diff HEAD~1(last commit) - Ask the user if a different scope is needed
- List all changed files and total lines changed
- Get recent changes:
-
Review for correctness (Critical/High):
- Logic errors: off-by-one, wrong comparisons, missing null checks
- Race conditions in async/concurrent code
- Resource leaks: unclosed connections, missing cleanup
- Error handling: swallowed errors, missing catch blocks, wrong error types
- Edge cases: empty arrays, zero values, undefined, boundary conditions
-
Review for security (Critical/High):
- Injection vulnerabilities (SQL, command, template)
- XSS: unescaped user input in output
- Hardcoded secrets or credentials
- Missing authentication or authorization checks
- Insecure defaults (permissive CORS, debug mode)
-
Review for performance (Medium):
- N+1 queries or unnecessary database calls
- Missing pagination on list endpoints
- Blocking operations in async contexts
- Unnecessary re-renders in React components
- Large objects in memory that could be streamed
-
Review for maintainability (Low/Medium):
- Functions exceeding ~50 lines
- Deeply nested conditionals (3+ levels)
- Duplicated logic that should be extracted
- Misleading variable or function names
- Missing type annotations on public APIs
-
Review for testing (Medium):
- New code paths without corresponding tests
- Modified behavior without updated tests
- Test assertions that don't actually verify the behavior
- Missing edge case tests for error handling
-
Format the review:
## Code Review Summary **Files reviewed:** X | **Issues found:** Y ### Critical - [file:line] [description] — [suggestion] ### High - [file:line] [description] — [suggestion] ### Medium - [file:line] [description] — [suggestion] ### Low - [file:line] [description] — [suggestion] ### Positive - [what was done well]
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.
- 4d ago First seen · 96 lines · 82 tokens per session scan A 310aae47f024
code-review is a skill published in the GitHub repository ao92265/claude-code-playbook (10 stars, last pushed 17d ago), licensed MIT. It adds 82 tokens to every session and 827 once invoked, about $0.0004 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…