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 MatrixFounder/Agentic-development --skill code-review-checklistgit clone --depth 1 https://github.com/MatrixFounder/Agentic-developmentWrote 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/matrixfounder/agentic-development/code-review-checklist)<a href="https://agentmods.dev/skills/matrixfounder/agentic-development/code-review-checklist"><img src="https://agentmods.dev/badge/skills/matrixfounder/agentic-development/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/matrixfounder/agentic-development/code-review-checklist"><img src="https://agentmods.dev/badge/skills/matrixfounder/agentic-development/code-review-checklist.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00021 | $0.01582 |
| Opus 5.5 | $0.00008 | $0.00633 |
| Sonnet 5.5 | $0.00004 | $0.00316 |
| Haiku 4.5 | $0.00002 | $0.00158 |
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 11d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Checklist
1. Task Compliance
- Requirements: Fulfills all "Changes Description" items?
- Acceptance Criteria: Met?
- Use Cases: Main scenario works?
2. Implementation Quality
- Top-Down/Stubs:
- Stub Task: Returns hardcoded values? NO logic? E2E checks hardcode?
- Impl Task: Real logic replaces stub? E2E updated?
- No Duplication: used existing methods/helpers?
- Error Handling: Exceptions caught and logged?
- Code Smells: No magic numbers, understandable names?
- Dead Code: Before proposing a deletion — symbol grepped repo-wide? (callout below)
Before acting on a "remove dead code" finding
- Grep the symbol repo-wide — never scope the search to a test directory. Tests are not always in one: Go keeps
*_test.gobeside the source, Rust puts unit tests inline under#[cfg(test)], JS/TS co-locates*.spec.ts/__tests__/, Python usestests/, Foundry usestest/*.t.sol. A directory-scoped grep returns "nothing depends on it" precisely where that answer is wrong.- If a test drives it, the fix is not deletion — make production reach the branch (wire the flag, pass the parameter) so code and requirement agree.
- Report it as "unreachable and covered by test X", not "dead, delete". A finding can be right about the smell and wrong about the fix.
3. Documentation "First"
- Directory Docs:
.AGENTS.mdupdated for touched source directories under memory tracking policy (or bootstrap step recorded)? - Docstrings: Present for new classes/methods? (Google/JSDoc)
- Project Docs: README updated if architecture changed?
- Positional references: If this change touches BOTH an artifact and a document citing it by
line/offset/ordinal — were those references re-checked against the final state of the
change, and is any pre-edit quotation tagged with its revision? (
documentation-standards§4.1) The reviewer owns this one: the author's own check passes even when it ran too early.
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.
- 11d ago Changed · +4 lines 338a02e645f5
- 13d ago Changed · +25 lines 60943100ead7
- 1mo ago First seen · 76 lines · 21 tokens per session scan A 17080829b785
code-review-checklist is a skill published in the GitHub repository MatrixFounder/Agentic-development (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 1,582 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
autofix
Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.
08-debug
Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.
debug-workflow
Run the Maestro debugging workflow for investigation-heavy tasks.
perf-check
Run a Maestro-style performance assessment for hotspots, regressions, and optimization planning.
superpowers-zh
Use when constraining AI coding with Chinese TDD methodology, systematic debugging, code review, and verification workflows. Superpowers-zh: Chinese adaptation of the Superpowers AI-assisted programming skills and methodologies.
hatch3r-bug-fix
Step-by-step bug fix workflow. Diagnose root cause, implement minimal fix, write regression test. Use when fixing bugs, working on bug report issues, or when the user mentions a bug.