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/laurigates/claude-plugins/code-review-checklistnpx skills add laurigates/claude-plugins --skill code-review-checklistgit clone --depth 1 https://github.com/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/code-review-checklist)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/code-review-checklist"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/code-review-checklist.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.00038 | $0.00957 |
| Opus 5 | $0.00019 | $0.00478 |
| Sonnet 5 | $0.00008 | $0.00191 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
code-review-checklist 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 yesterday.
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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Checklist
Structured approach to reviewing code changes.
When to Use This Skill
| Use this skill when... | Use something else instead when... |
|---|---|
| Walking a priority-ordered manual review checklist | Running a full delegated review pass → code-review |
| Hunting for hardcoded secrets, injection, or N+1 query patterns | Scanning specifically for anti-patterns → code-antipatterns |
| Verifying error handling and edge cases in a PR diff | Targeting swallowed errors directly → code-hidden-failures --track errors |
| Applying a deterministic checklist to a small change | Refactoring after the checklist surfaces issues → code-refactor |
Review Priority Order
- Security (Critical) - Vulnerabilities, secrets, injection
- Correctness (High) - Logic errors, breaking changes
- Performance (Medium) - Inefficiencies, resource leaks
- Quality (Medium) - Maintainability, readability
- Style (Low) - Formatting, naming (should be automated)
Security Checklist
Secrets & Credentials
- No hardcoded API keys, passwords, tokens
- No credentials in logs or error messages
- Secrets loaded from environment/vault
Injection Vulnerabilities
- SQL queries use parameterized statements
- User input is sanitized before HTML output (XSS)
- Shell commands don't include user input (command injection)
- File paths are validated (path traversal)
Authentication & Authorization
- Auth checks on all protected endpoints
- Proper session handling
- Secure password handling (hashing, not plaintext)
Data Exposure
- Sensitive data not logged
- API responses don't leak internal details
- Error messages don't expose system info
Correctness Checklist
Logic
- Edge cases handled (null, empty, boundary values)
- Error conditions handled appropriately
- Async operations properly awaited
- Race conditions considered
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.
- yesterday First seen · 139 lines · 38 tokens per session scan A 9612e7e89e9c
code-review-checklist is a skill published in the GitHub repository laurigates/claude-plugins (57 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 957 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
plan
Produce structured implementation plans with goal, approach, test strategy, blast-radius assessment, parallelism analysis, and a user approval gate before any code is written. Persisting PLAN.md for fresh-session handoff. Use when: 'plan this', 'architect this', 'how should we implement', 'implementation plan', 'write…
extract-ssot
Deduplicate repeated markdown content, rule files, skill bodies, ADRs, docs, into a single named source of truth and migrate every call site to cite it by exact heading. Use when the same prose, literal, or concept appears (or is reworded) across files: 'DRY this prose', 'extract a shared rule', 'single source of…
map-corpus
Map a multi-resource documentation corpus into a verified, classified, triaged slice BEFORE any digesting: bounded discovery (llms.txt + sitemap), a user-approved link map classifying every discovered URL, deterministic node manifests over immutable snapshots, and a per-node relevance inventory whose evidence a script…
feature-branch-pr-writing
Use this skill when the user asks to write, draft, create, or improve a PR description for a Shopware core repository PR — AND that PR targets a non-trunk feature branch (not trunk itself). Trigger phrases like "write a PR description", "draft the PR", "what should I put in the PR body". The skill detects the target…
ci-log-interpretation
Use this skill when reading or analyzing CI logs from a Shopware GitHub Actions workflow to figure out why a build failed — phrases like "why did CI fail", "what broke the build", "check the pipeline", "interpret these logs", "debug this red build" — or whenever raw run logs, job logs, or check annotations from a…
repo-activity
Scan all git repositories under /repos and report recent activity — last commit age, branch, uncommitted changes — in age-bucketed tables. Use when the user asks for a repo activity overview, "what have I been working on", portfolio status, or which repos are active/dormant.