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/commands/vinvcn/addyosmani-agent-skills-zh/review)<a href="https://agentmods.dev/commands/vinvcn/addyosmani-agent-skills-zh/review"><img src="https://agentmods.dev/badge/commands/vinvcn/addyosmani-agent-skills-zh/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/vinvcn/addyosmani-agent-skills-zh/review"><img src="https://agentmods.dev/badge/commands/vinvcn/addyosmani-agent-skills-zh/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.00016 | $0.00202 |
| Opus 5 | $0.00008 | $0.00101 |
| Sonnet 5 | $0.00003 | $0.00040 |
| Haiku 4.5 | $0.00002 | $0.00020 |
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 12d 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
调用 agent-skills:code-review-and-quality skill。
围绕全部五个轴 review 当前变更（staged 或 recent commits）：
- Correctness — 是否匹配 spec？edge cases 是否处理？tests 是否充分？
- Readability — 命名是否清晰？逻辑是否直接？组织是否良好？
- Architecture — 是否遵循现有 patterns？boundaries 是否清晰？abstraction level 是否合适？
- Security — 输入是否验证？secrets 是否安全？auth 是否检查？（使用 security-and-hardening skill）
- Performance — 是否没有 N+1 queries？是否没有 unbounded ops？（使用 performance-optimization skill）
将 findings 分类为 Critical、Important 或 Suggestion。 输出结构化 review，包含具体 file:line references 和 fix recommendations。
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.
- 12d ago First seen · 17 lines · 16 tokens per session scan A 361e0a2ddae3
review is a command published in the GitHub repository vinvcn/addyosmani-agent-skills-zh (31 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 202 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
review
Conduct a five-axis code review — correctness, readability, architecture, security, performance.
code-simplify
Simplify code for clarity and maintainability — reduce complexity without changing behavior.
review
Conduct a five-axis code review — correctness, readability, architecture, security, performance.
ship
Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision.
plan
Break work into small verifiable tasks with acceptance criteria and dependency ordering.
build
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.