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/block/agent-skills/code-reviewnpx skills add block/agent-skills --skill code-reviewgit clone --depth 1 https://github.com/block/agent-skillsWhat 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.00011 | $0.00243 |
| Opus 5 | $0.00005 | $0.00121 |
| Sonnet 5 | $0.00002 | $0.00049 |
| Haiku 4.5 | $0.00001 | $0.00024 |
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 2d 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.
What it actually says
Code Review Checklist
When reviewing code, check each of these areas:
Functionality
- Code does what the PR description claims
- Edge cases are handled
- Error handling is appropriate
Code Quality
- Follows project style guide
- No hardcoded values that should be configurable
- Functions are focused and well-named
Testing
- New functionality has tests
- Tests are meaningful, not just for coverage
- Existing tests still pass
Security
- No credentials or secrets in code
- User input is validated
- SQL queries are parameterized
Performance
- No obvious performance issues
- Database queries are optimized
- No unnecessary loops or iterations
Documentation
- Public APIs are documented
- Complex logic has comments explaining "why"
- README updated if needed
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.
- 2d ago First seen · 51 lines · 11 tokens per session scan A 0ea793c39def
code-review is a skill published in the GitHub repository block/agent-skills (23 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 243 once invoked, about $0.0001 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
plugin-quality
审查和改进 Zhin.js 插件质量（Plugin Runtime）。Use when asked to review plugin code, audit structure, or improve before publishing. 检查 definePlugin、约定目录、发送链与安全。.
code-review
Code review for issues, style consistency, best practices—use for full code evaluation; not for debugging specific errors or fixing individual style violations.
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.
fin-review-loop
经济金融论文的对抗性review循环。对草稿进行多轮严格评审，检查实证严谨性、方法正确性、理论贡献和写作质量，给出可操作的修改建议。（AI review 不能替代同行评审，草稿必须经研究者核实后投稿。）.
plugin-test
为 Zhin.js 插件编写和运行测试（Plugin Runtime）。Use when asked to write tests, add test coverage, or verify defineCommand / definePlugin behavior. 引导编写符合 Runtime 的 Vitest 测试。.