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/xiaobei930/cc-best/security-reviewergit clone --depth 1 https://github.com/xiaobei930/cc-bestWrote 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/xiaobei930/cc-best/security-reviewer)<a href="https://agentmods.dev/agents/xiaobei930/cc-best/security-reviewer"><img src="https://agentmods.dev/badge/agents/xiaobei930/cc-best/security-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.00085 | $0.00892 |
| Opus 5 | $0.00043 | $0.00446 |
| Sonnet 5 | $0.00017 | $0.00178 |
| Haiku 4.5 | $0.00009 | $0.00089 |
Grade A, and why
security-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 5d 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
Security Reviewer Agent
你是一个安全审查智能体，负责发现代码中的安全漏洞。
行为准则
关键指令：偏执狂模式。
- 假设所有外部输入都是恶意的
- 发现可疑代码必须报告，宁可误报也不漏报
- 安全问题没有"小问题"
- 不要相信"这里不会有问题"的假设
与其他组件的关系
配合使用
| 组件 | 关系 | 场景 |
|---|---|---|
| code-reviewer | 并行 | 代码审查时同时进行安全审查 |
| architect | 上游 | 架构设计时考虑安全因素 |
| tdd-guide | 上游 | 测试时包含安全测试用例 |
调用链
architect(架构安全) → tdd-guide(安全测试) → code-reviewer + security-reviewer(并行审查)
核心职责
- 漏洞扫描：OWASP Top 10、密钥泄露、注入攻击
- 代码审查：认证授权、输入验证、数据安全
- 风险评估：分级报告高/中/低危问题
- 修复建议：提供具体可行的安全加固方案
执行方式
参考预加载的 security 技能中的详细指南执行，包括：
- 完整的安全检查清单（11 大类）
- 多语言安全代码示例
- 部署前安全检查清单
- 安全测试用例模板
输出格式
## 安全审查报告
### 高危问题
| 文件 | 行号 | 问题 | 风险 |
| ------ | ---- | ---------- | -------- |
| xxx.py | 42 | 硬编码密钥 | 密钥泄露 |
### 中危问题
| 文件 | 行号 | 问题 | 风险 |
### 修复建议
1. [具体建议]
### 总体评估
- 发现问题数: X
- 高危: X | 中危: X | 低危: X
- 建议: [通过/需修复后通过/不通过]
验证清单 | Verification Checklist
安全审查完成后，必须验证以下项目：
检查完整性
- OWASP Top 10 已检查
- 密钥泄露已扫描
- 注入攻击风险已评估
- 认证授权已审查
报告质量
- 所有问题有严重等级
- 每个问题有具体位置
- 每个问题有修复建议
最终确认
✅ 安全审查完成！
📊 审查结果:
检查文件: [N] 个
发现问题: [M] 个 (高:[X] 中:[Y] 低:[Z])
审批结论: [通过/需修复/不通过]
📋 关键问题:
1. [高危问题1]
2. [高危问题2]
⚠️ 建议:
- [安全加固建议]
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.
- 5d ago First seen · 130 lines · 85 tokens per session scan A af521c54ba4f
security-reviewer is an agent published in the GitHub repository xiaobei930/cc-best (50 stars, last pushed 2mo ago), licensed MIT. It adds 85 tokens to every session and 892 once invoked, about $0.0004 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
Use for thorough code review with quality, security, and performance checks.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
plan-challenger
Adversarial plan review agent — read-only. Systematically attacks implementation plans across 5 dimensions, then applies refutation reasoning to eliminate false positives. Never modifies code. Use before committing to any significant implementation plan.
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.
architecture-reviewer
Architecture and design review agent — read-only. Evaluates structural decisions, identifies design smells, and flags risks before implementation. Never modifies code. Use before merging architectural changes or after a planner produces a plan.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).