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.
git clone --depth 1 https://github.com/echoVic/blade-codeWrote 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/commands/echovic/blade-code/review)<a href="https://agentmods.dev/commands/echovic/blade-code/review"><img src="https://agentmods.dev/badge/commands/echovic/blade-code/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/commands/echovic/blade-code/review"><img src="https://agentmods.dev/badge/commands/echovic/blade-code/review.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.00006 | $0.00298 |
| Opus 5.5 | $0.00002 | $0.00119 |
| Sonnet 5.5 | $0.00001 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
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 1mo 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
请对以下变更进行代码审查。
变更范围
$ARGUMENTS
当前 Diff
!`git diff $ARGUMENTS 2>/dev/null || git diff`
审查要点
请从以下维度进行审查：
1. 代码质量
- 命名是否清晰
- 函数是否过长
- 是否有重复代码
- 是否符合 SOLID 原则
2. 潜在 Bug
- 边界条件处理
- 空值检查
- 类型安全
- 并发问题
3. 安全性
- 输入验证
- SQL 注入
- XSS 风险
- 敏感信息暴露
4. 性能
- 不必要的循环
- 内存泄漏
- N+1 查询
- 大对象拷贝
5. 可维护性
- 注释是否充分
- 测试覆盖
- 错误处理
请给出具体的改进建议，并标注优先级（🔴 高 / 🟡 中 / 🟢 低）。
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.
- 1mo ago First seen · 57 lines · 6 tokens per session scan A 2b55346081ea
review is a command published in the GitHub repository echoVic/blade-code (180 stars, last pushed 3d ago), licensed MIT. It adds 6 tokens to every session and 298 once invoked, about $0.0000 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-30.
Other commands, from other repositories
speckit.review
Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.
speckit.review.code
General code quality review — project guideline compliance, bug detection, code quality analysis.
speckit.converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
review-pr
Comprehensive PR review using specialized agents.
code-review
Code review a pull request.
checklist
Generate a custom checklist for the current feature based on user requirements.