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 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 6 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.1 | $0.00038 | $0.00957 |
| Opus 5.5 | $0.00015 | $0.00383 |
| Sonnet 5.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 1mo 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 — 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.
- 1mo ago 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 (59 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 957 once invoked, about $0.0002 per session on Opus 5.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
review-feedback
Address code review/PR comments: verify each, then fix.
phpunit-test-team-reviewing
Use this skill when the user asks for a team-based, consensus, multi-reviewer, or red-team review of Shopware PHPUnit tests — trigger phrases like "team review these tests", "consensus review the tests in PR.
phpunit-test-reconciling
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
audit-comment-residue
Read-only classifier that flags residue in code comments: history narration, plan or session references, conversational asides, ticket or PR back-references, origin notes, and workarounds with no link or removal condition. Use when asked to 'audit code comments' or report which comments only make sense with the chat…
issue-analyzing
Use this skill when the user asks to analyze a specific GitHub issue, understand what area of code an issue affects, assess an issue's scope, or research the code context around an issue — example triggers like "analyze issue.
pr-analyzing
Use this skill when the user asks to analyze a specific GitHub pull request, review a PR's architectural impact, assess what changed in a PR and why it matters, or research the code relationships affected by a PR — example triggers like "analyze PR.