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 vitoworleone/claude-code-handbook --skill reviewgit clone --depth 1 https://github.com/vitoworleone/claude-code-handbookWrote 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/vitoworleone/claude-code-handbook/review)<a href="https://agentmods.dev/skills/vitoworleone/claude-code-handbook/review"><img src="https://agentmods.dev/badge/skills/vitoworleone/claude-code-handbook/review/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/vitoworleone/claude-code-handbook/review"><img src="https://agentmods.dev/badge/skills/vitoworleone/claude-code-handbook/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00007 | $0.00428 |
| Opus 5 | $0.00003 | $0.00214 |
| Sonnet 5 | $0.00001 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
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 9d 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
任务
你需要审查当前代码变更。
步骤
- 运行
git diff查看未暂存变更，运行git diff --staged查看已暂存变更 - 如果两者都为空，运行
git log -1 --format=%H获取最近一次提交，再git diff HEAD~1查看 - 逐文件审查变更，按以下五个维度分析：
- 逻辑正确性：算法是否正确、边界条件是否处理、空值/异常是否覆盖
- 安全性：是否有注入漏洞、敏感信息泄露、权限问题
- 性能：是否有不必要的循环、N+1 查询、内存泄漏风险
- 代码风格：命名是否清晰、是否符合项目约定、是否有重复代码
- 可维护性：抽象是否合理、依赖是否清晰、是否易于测试
- 按严重程度分级报告：
- Critical：必须修复，存在正确性或安全性问题
- Warning：建议修复，存在潜在风险或明显改进空间
- Info：可以改进，代码质量建议
- 代码质量好的部分也给出正面反馈
输出格式
## 审查报告
### Critical
- [文件:行号] 问题描述及修复建议
### Warning
- [文件:行号] 问题描述及修复建议
### Info
- [文件:行号] 改进建议
### 正面反馈
- 值得肯定的设计或实现
$ARGUMENTS
What ships with it
1 file 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.
- 9d ago First seen · 52 lines · 7 tokens per session scan A 0a76cd452bc2
review is a skill published in the GitHub repository vitoworleone/claude-code-handbook (45 stars, last pushed 6d ago), licensed MIT. It adds 7 tokens to every session and 428 once invoked, about $0.0000 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
simplify
Review recent code changes for reuse, code quality, and efficiency, then directly apply straightforward cleanup improvements. Use when the user wants a post-implementation cleanup pass, pre-PR polish, or asks to simplify/refine recent changes. Invoke with /simplify or /simplify .
triage
Gatekeep and review GitHub issues and pull requests for Qwen Code maintainers. Use for GitHub Action issue triage, PR admission checks, product-direction review, KISS-focused PR review, and staged bilingual GitHub comments.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
autofix
Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.
agentic-code-review
Use when reviewing a diff, pull request, branch, or AI-generated code for correctness, security, regression, test, performance, and maintainability risks before merge.
repo-health-check
Use when auditing a repo before changes to find the smallest safe PR, quality risks, stale docs, missing tests, ignored-file gaps, or agent setup issues. Best first skill for unfamiliar codebases.