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 commands/ysicing/code-pilot/reviewgit clone --depth 1 https://github.com/ysicing/code-pilotWhat 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.00017 | $0.00468 |
| Opus 5 | $0.00009 | $0.00234 |
| Sonnet 5 | $0.00003 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
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 yesterday.
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
使用方法
/review <CODE_SCOPE>
上下文
- 代码审查范围：$ARGUMENTS
- 目标文件将使用 @file 语法引用
- 将考虑项目编码标准和约定
您的角色
您是代码审查协调员，指导四位审查专家：
- 质量审核员 (基于reviewer子代理) – 遵循 Evidence-First、Clean Code 原则和官方风格指南的代码质量评估
- 安全分析师 – 识别漏洞和安全最佳实践
- 性能审查员 – 评估效率和优化机会
- 架构评估师 – 验证设计模式和结构决策
流程
- 代码检查：系统化分析目标代码段和依赖关系。
- 多维度审查：
- 质量审核员：MECE 审查视角 (正确性·可读性·可维护性·效率性)，官方风格指南遵循，基于指标评估
- 安全分析师：扫描注入风险、认证问题和数据泄露
- 性能审查员：识别瓶颈、内存泄漏和优化点
- 架构评估师：评估 SOLID 原则、模式和可扩展性
- 综合分析：将发现整合为优先级明确的可执行反馈。
- 验证：确保建议实用且符合项目目标。
输出格式
- 审查摘要 – 高层评估和优先级分类。
- 详细发现 – 具体问题，包含代码示例和解释。
- 改进建议 – 具体重构建议，包含代码样例。
- 行动计划 – 优先任务，包含工作量估算和影响评估。
- 后续行动 – 跟进审查和监控需求。
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.
- yesterday First seen · 37 lines · 17 tokens per session scan A 9036665177cc
review is a command published in the GitHub repository ysicing/code-pilot (38 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 468 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 commands, from other repositories
specify
Create or update the feature specification from a natural language feature description.
speckit.git.validate
Validate current branch follows feature branch naming conventions.
pr-address
Address PR review comments on current branch.
plan-save
Save the current session's plan to GitHub as an issue.
enforce_standards
CRITICAL: Before running the code standards enforcer, we must prepare the stack properly and abort if there are merge conflicts.
OPSX: Sync
Sync delta specs from a change to main specs.