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 skills/garyfigno/dr.wangagent/code-reviewnpx skills add GaryFigno/Dr.WangAgent --skill code-reviewgit clone --depth 1 https://github.com/GaryFigno/Dr.WangAgentWhat 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.00049 | $0.00433 |
| Opus 5 | $0.00024 | $0.00217 |
| Sonnet 5 | $0.00010 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00043 |
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 2d 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
代码审查清单
先定位范围
- 用户没指定文件时，用
git diff --stat HEAD或最近改动定位本次要审的代码 - 每次只审一个明确的变更集，不把无关代码卷进来
逐条核对（按顺序）
- 行为正确性：逻辑分支是否有遗漏、边界条件（空输入 / 并发 / 失败路径）是否处理
- 错误处理：异常是否被吞掉；失败时是否有用户可见的提示
- 安全性：是否有密钥/路径注入、命令拼接、越权文件访问；用户输入是否被转义
- 性能：是否有无界循环、重复 IO、把大文件整读进内存等明显问题
- 可维护性：魔法数字、复制粘贴代码、超长函数、命名是否达意
- 测试：改动是否缺测试；已有测试是否真的覆盖了改动路径
输出格式
对每条发现给出：
[严重/建议/疑问] 文件:行号 — 问题描述
建议：怎么改
- 严重：会导致错误行为、数据丢失或安全问题，必须修
- 建议：能改得更好，但不阻塞
- 疑问：需要作者澄清，不是结论
最后给一个总评（1-3 句）+ 是否建议合并。不要为了凑条数而挑刺，也不要漏掉真问题。
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.
- 2d ago First seen · 37 lines · 49 tokens per session scan A 712b334816bd
code-review is a skill published in the GitHub repository GaryFigno/Dr.WangAgent (2 stars, last pushed 14d ago), licensed MIT. It adds 49 tokens to every session and 433 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-31.
Other skills, from other repositories
cut-release
Decide whether unreleased develop work warrants a release, pick the version per semver.org, and cut it following this repo's established commit/PR/tag/release pattern.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.