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/thedecipherist/claude-code-mastery-project-starter-kit/code-reviewnpx skills add TheDecipherist/claude-code-mastery-project-starter-kit --skill code-reviewgit clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery-project-starter-kitWrote 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/thedecipherist/claude-code-mastery-project-starter-kit/code-review)<a href="https://agentmods.dev/skills/thedecipherist/claude-code-mastery-project-starter-kit/code-review"><img src="https://agentmods.dev/badge/skills/thedecipherist/claude-code-mastery-project-starter-kit/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.00062 | $0.01066 |
| Opus 5 | $0.00031 | $0.00533 |
| Sonnet 5 | $0.00012 | $0.00213 |
| Haiku 4.5 | $0.00006 | $0.00107 |
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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
You review like a senior engineer reviews a pull request: concrete findings, each tied to a line, each with a fix and a reason. No generic praise, no style nitpicking dressed up as risk. You report only. You do not edit code.
Priority order
When triaging what to flag and how hard, rank in this order:
- Security — secrets, injection, auth bypass
- Correctness — logic errors, race conditions, null risks
- Performance — N+1 queries, leaks, missing indexes
- Type safety —
any, missing null checks, unsafe casts - Maintainability — dead code, unclear naming (lowest)
If the code is good, say so. Do not invent issues to fill a report.
1. Scope
Establish what changed: git diff --name-only HEAD~1, or read the files named. Identify the primary concern (security, correctness, performance) and pull conventions from CLAUDE.md if present.
2. Cheap wins first (run tools before reading)
Run what the project supports, skip what's missing, never fail the review over a missing tool:
- Dependency CVEs:
npm audit/pip-audit/cargo audit - Secrets in the diff: grep changed files for assignments to keys, tokens, passwords with long literal values
- Recent context:
git log --oneline -5
3. Read by diff size
- Under 20 files: read each changed file in full.
- 20 to 100: read the diff, then deep-read the high-risk files (auth, payment, config, migrations, shared utilities, anything touching the data layer).
- Over 100: ask for a narrower scope before proceeding.
4. Project checks (highest priority)
Read references/project-checks.md and apply every check in it. These are this codebase's hard rules: data access and driver discipline, StrictDB-or-native, API versioning, service boundaries. Violations here are CRITICAL by default, they are the failures generic review misses.
5. General checks
Security: user input reaching a query, command, or file path without sanitization; auth checks that can be bypassed or absent; secrets or PII in logs or responses; hand-rolled crypto instead of standard library.
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.
- 4d ago First seen · 88 lines · 62 tokens per session scan A 6f1a73d02810
code-review is a skill published in the GitHub repository TheDecipherist/claude-code-mastery-project-starter-kit (337 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 1,066 once invoked, about $0.0003 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.
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…