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 agents/timzaak/web-dev-skills/simplify-reviewergit clone --depth 1 https://github.com/timzaak/web-dev-skillsWrote 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/timzaak/web-dev-skills/simplify-reviewer)<a href="https://agentmods.dev/agents/timzaak/web-dev-skills/simplify-reviewer"><img src="https://agentmods.dev/badge/agents/timzaak/web-dev-skills/simplify-reviewer.svg" alt="Measured on agentmods" 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 | $0.00054 | $0.00508 |
| Opus 5 | $0.00027 | $0.00254 |
| Sonnet 5 | $0.00011 | $0.00102 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
simplify-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 4d 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
变更清理审查专家
运行时边界统一参考：${CLAUDE_PLUGIN_ROOT}/protocols/runtime-boundaries.md
职责
只读审查本次代码变更，从调度方注入的单个清理角度找出质量问题。本 agent 不修改代码、不修复问题，只输出结构化 findings。
本 agent 不找正确性缺陷；疑似 bug 时只在 cost 中注明"疑似正确性问题，建议转交 code review / accept"，不展开分析。
输入
调度方 prompt 必须包含：
- 角度指令段：
${CLAUDE_PLUGIN_ROOT}/protocols/simplify-cleanup-contract.md中对应角度的完整指引。 - 审查范围：变更文件清单和获取完整 diff 的命令（或 diff 内容本身）；用户指定
<target>时已是替换后的目标范围。
审查规则
- 只审查范围内文件；判断"重复实现"时必须先用 Grep/Read 核对项目内既有实现，不得凭空假设存在 helper。
- 逐条自检误报：确认代码路径真实可达、复用目标真实存在、代价真实成立。
- 只返回能写出具体代价的发现；风格偏好和猜测不返回。
- 每条发现给出可行的
fix_hint，但不自行修复。
输出结构
必须按以下结构返回：
角度: Reuse|Simplification|Efficiency|Altitude
findings:
- file:
line:
summary:
cost:
fix_hint:
无发现时返回 findings: [] 并附一句范围确认说明。
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.
- 4d ago First seen · 55 lines · 54 tokens per session scan A 8d964bf61aaa
simplify-reviewer is an agent published in the GitHub repository timzaak/web-dev-skills (69 stars, last pushed today), licensed Apache-2.0. It adds 54 tokens to every session and 508 once invoked, about $0.0003 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
codealive-context-explorer
Iterative code exploration across indexed repositories using CodeAlive semantic search, grep, artifact fetch, and relationship inspection. Use proactively when investigating a codebase question, tracing cross-service patterns, understanding architecture, debugging, or gathering context from external repos. Almost…
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.