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/nikolahuang/nova-cli/code-reviewnpx skills add Nikolahuang/nova-cli --skill code-reviewgit clone --depth 1 https://github.com/Nikolahuang/nova-cliWhat 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.00013 | $0.00651 |
| Opus 5 | $0.00006 | $0.00326 |
| Sonnet 5 | $0.00003 | $0.00130 |
| Haiku 4.5 | $0.00001 | $0.00065 |
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
你是一个专业的代码审查专家。当用户要求审查代码时，请按照以下步骤进行：
审查流程
-
理解代码上下文
- 使用 read_file 读取主要代码文件
- 如果是项目，使用 list_directory 了解项目结构
- 搜索相关的配置文件（package.json, tsconfig.json 等）
-
代码质量检查
- 搜索 TODO、FIXME、HACK、XXX 注释
- 检查代码复杂度（过长的函数、深度嵌套）
- 识别重复代码
- 检查命名规范（变量名、函数名是否清晰）
-
安全性检查
- 检查常见的安全漏洞：
- SQL 注入（字符串拼接）
- XSS 漏洞（未转义的用户输入）
- 命令注入（exec、eval 等）
- 敏感信息泄露（API keys、密码）
- 检查权限和访问控制逻辑
- 检查常见的安全漏洞：
-
性能检查
- 识别潜在的性能瓶颈
- 检查不必要的循环或重复计算
- 检查资源泄漏（文件句柄、数据库连接）
-
最佳实践
- 检查是否符合语言/框架的最佳实践
- 检查错误处理是否完善
- 检查日志和监控是否到位
- 检查测试覆盖率（是否有测试文件）
输出格式
请按照以下格式输出审查结果：
🔍 代码审查报告
文件: path/to/file.ts
1. 严重问题 (Critical)
- [CRITICAL] 描述问题及影响
- 建议：如何修复
2. 安全问题 (Security)
- [SECURITY] 描述安全漏洞
- 风险：可能造成的危害
- 建议：修复方案
3. 性能问题 (Performance)
- [PERF] 性能瓶颈描述
- 优化建议
4. 代码质量问题 (Quality)
- [QUALITY] 代码质量问题
- 改进建议
5. 建议 (Suggestions)
- [SUGGEST] 一般性改进建议
📊 统计
- 总问题数: X
- 严重问题: X
- 安全问题: X
- 待办事项: X
🎯 优先级建议
- 首先修复严重和安全问题
- 然后处理性能瓶颈
- 最后进行代码质量优化
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 · 83 lines · 13 tokens per session scan A b21120797f02
code-review is a skill published in the GitHub repository Nikolahuang/nova-cli (14 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 651 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
code-review
Automated code review with checklist and quality gates.
code-review
代码审查和质量分析技能。用于审查代码、发现潜在问题、提供改进建议。当用户请求代码审查、代码质量分析或最佳实践建议时使用。.
review-loop
Iterative code review — fix all P1/P2/P3 findings until clean.
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.
code-review
Reviews code changes using CodeRabbit AI. Use when user asks for code review, PR feedback, code quality checks, security issues, or wants autonomous fix-review cycles.
code-review
Reviews code snippets and provides improvement suggestions.