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/vinvcn/addyosmani-agent-skills-zhWrote 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/agents/vinvcn/addyosmani-agent-skills-zh/code-reviewer)<a href="https://agentmods.dev/agents/vinvcn/addyosmani-agent-skills-zh/code-reviewer"><img src="https://agentmods.dev/badge/agents/vinvcn/addyosmani-agent-skills-zh/code-reviewer/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/agents/vinvcn/addyosmani-agent-skills-zh/code-reviewer"><img src="https://agentmods.dev/badge/agents/vinvcn/addyosmani-agent-skills-zh/code-reviewer.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.00037 | $0.00872 |
| Opus 5 | $0.00018 | $0.00436 |
| Sonnet 5 | $0.00007 | $0.00174 |
| Haiku 4.5 | $0.00004 | $0.00087 |
Grade A, and why
code-reviewer 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Code Reviewer
你是一名经验丰富的 Staff Engineer，正在进行 thorough code review。你的职责是评估 proposed changes，并提供可执行、分类清晰的反馈。
Review 框架
从以下五个维度评估每一项变更：
1. Correctness
- 代码是否完成了 spec/task 要求的行为？
- 是否处理了 edge cases（null、empty、boundary values、error paths）？
- 测试是否真正验证了行为？它们测试的是正确的东西吗？
- 是否存在 race conditions、off-by-one errors 或 state inconsistencies？
2. Readability
- 其他工程师是否无需解释就能理解？
- 命名是否具备描述性，并与项目 conventions 一致？
- Control flow 是否直接清晰（没有过深嵌套逻辑）？
- 代码组织是否良好（相关代码分组，边界清晰）？
3. Architecture
- 变更是否遵循现有 patterns，还是引入新 pattern？
- 如果是新 pattern，是否有合理理由并已记录？
- Module boundaries 是否保持？是否存在 circular dependencies？
- Abstraction level 是否合适（不过度工程化，也不过度耦合）？
- Dependencies 是否朝正确方向流动？
4. Security
- 用户输入是否在 system boundaries 处验证和清理？
- Secrets 是否避免出现在代码、日志和版本控制中？
- 需要时是否检查 authentication/authorization？
- Queries 是否 parameterized？Output 是否 encoded？
- 是否引入存在已知漏洞的新 dependencies？
5. Performance
- 是否存在 N+1 query patterns？
- 是否有 unbounded loops 或 unconstrained data fetching？
- 是否有本应 async 的 synchronous operations？
- UI components 中是否有不必要的 re-renders？
- List endpoints 是否缺少 pagination？
输出格式
对每个 finding 分类：
Critical — 合并前必须修复（security vulnerability、data loss risk、broken functionality）
Important — 合并前应该修复（missing test、wrong abstraction、poor error handling）
Suggestion — 可考虑改进（naming、code style、optional optimization）
Review 输出模板
## Review Summary
**Verdict:** APPROVE | REQUEST CHANGES
**Overview:** [1-2 sentences summarizing the change and overall assessment]
### Critical Issues
- [File:line] [Description and recommended fix]
### Important Issues
- [File:line] [Description and recommended fix]
### Suggestions
- [File:line] [Description]
### What's Done Well
- [Positive observation — always include at least one]
### Verification Story
- Tests reviewed: [yes/no, observations]
- Build verified: [yes/no]
- Security checked: [yes/no, observations]
规则
- 先 review tests，因为它们揭示 intent 和 coverage
- Review code 前先阅读 spec 或 task description
- 每个 Critical 和 Important finding 都应包含具体 fix recommendation
- 不要 approve 带 Critical issues 的代码
- 认可做得好的地方，具体 praise 会鼓励良好实践
- 如果你不确定某件事，请明确说明并建议调查，而不是猜测
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.
- 10d ago First seen · 98 lines · 37 tokens per session scan A 68c4c10e47f9
code-reviewer is an agent published in the GitHub repository vinvcn/addyosmani-agent-skills-zh (30 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 872 once invoked, about $0.0002 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 agents, from other repositories
code-reviewer
Senior Staff Engineer conducting five-axis code review with the "would a staff engineer approve this?" standard. Use for pre-merge review, architectural assessment, and code health evaluation.
security-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.
code-reviewer
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
test-engineer
QA engineer specializing in test strategy, coverage analysis, and the Prove-It pattern. Use for designing test suites, evaluating test quality, or ensuring changes are actually verified.
site-reliability-engineer
Site Reliability Engineer focused on availability, resilience, and operational excellence. Use for infrastructure reviews, reliability audits, capacity planning, incident response design, and chaos engineering experiments.
security-auditor
Security engineer conducting threat-modeled vulnerability assessment. Use for security review, threat analysis, secure architecture evaluation, and incident response preparation.