code-review

A structured review of code changes using four checks: risk, resilience, readability, and reliability. It produces a review report for the change.

In plain words
What is it for?
It reads the implementation check and the Git changes, records findings in a review document, and waits for people to confirm that issues have been fixed.
Why use it?
It helps find security issues, edge cases, recovery problems, confusing code, and missing or inconsistent tests before the work is accepted.

Command

Install

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.

agentmods
npx agentmods add commands/alisunstar/opensunstar/code-review
Clone the repo
git clone --depth 1 https://github.com/alisunstar/OpenSunstar
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 171 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00171
Opus 5 $0.00000 $0.00086
Sonnet 5 $0.00000 $0.00034
Haiku 4.5 $0.00000 $0.00017

Measured yesterday against content hash a3fa75b4f9d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

rd-protocol/commands/code-review.md · 21 lines

What it actually says

/rd:code-review — 代码审查

阶段 6a:多维度代码审查(4R lenses)。

先读

  • .specs/<change-id>/IMPLEMENTATION-CHECK.md
  • git diff

执行

按 4R lenses 审查:

  • review-risk — 风险点(边界/异常/安全)
  • resilience — 健壮性(容错/恢复)
  • readability — 可读性(命名/结构/注释)
  • reliability — 可靠性(测试/一致性)

产物

  • .specs/<change-id>/REVIEW.md

人工确认

— 审查问题需修复后确认。

Changes

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.

  1. yesterday First seen · 21 lines · 0 tokens per session scan A a3fa75b4f9d8

Subscribe to this mod's changes

code-review is a command published in the GitHub repository alisunstar/OpenSunstar (40 stars, last pushed 18d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 171 tokens. 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.