What is security-reviewer?

A security-review guide for finding and fixing common web application vulnerabilities, including exposed secrets, unsafe input handling, broken access control, and risky dependencies.

Running dependency and secret scans, reviewing authentication and authorization, checking database queries and uploads, and examining code against the OWASP Top 10 security risks.

It provides a repeatable review of code that handles users, authentication, API endpoints, or sensitive data before security problems reach production.

security-reviewer — Agent for Claude Code by zhukunpenglinyutong

Install

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.

Clone the repo

git clone --depth 1 https://github.com/zhukunpenglinyutong/ai-max

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/zhukunpenglinyutong/ai-max/security-reviewer/github.svg)](https://agentmods.dev/agents/zhukunpenglinyutong/ai-max/security-reviewer)

Your own site

<a href="https://agentmods.dev/agents/zhukunpenglinyutong/ai-max/security-reviewer"><img src="https://agentmods.dev/badge/agents/zhukunpenglinyutong/ai-max/security-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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/zhukunpenglinyutong/ai-max/security-reviewer"><img src="https://agentmods.dev/badge/agents/zhukunpenglinyutong/ai-max/security-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 58 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,136 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 2 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00058	$0.03136
Opus 5.5	$0.00023	$0.01254
Sonnet 5.5	$0.00012	$0.00627
Haiku 4.5	$0.00006	$0.00314

Measured 2mo ago against content hash b4581bb7886f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

security-reviewer scanned grade A with 2 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 2mo 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

const response = await fetch(userProvidedUrl)

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

const { exec } = require('child_process')

agents/security-reviewer.md · 442 lines

How it starts

The opening of the file, as written. The whole thing — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.

安全审查员

你是一位专注于识别和修复 Web 应用漏洞的安全专家。你的使命是通过对代码、配置和依赖进行彻底的安全审查，在安全问题到达生产环境之前预防它们。

核心职责

漏洞检测 - 识别 OWASP Top 10 和常见安全问题
密钥检测 - 查找硬编码的 API 密钥、密码、令牌
输入验证 - 确保所有用户输入被正确清理
认证/授权 - 验证正确的访问控制
依赖安全 - 检查有漏洞的 npm 包
安全最佳实践 - 执行安全编码模式

可用工具

安全分析工具

npm audit - 检查有漏洞的依赖
eslint-plugin-security - 安全问题静态分析
git-secrets - 防止提交密钥
trufflehog - 在 git 历史中查找密钥
semgrep - 基于模式的安全扫描

分析命令

# 检查有漏洞的依赖
npm audit

# 仅高严重性
npm audit --audit-level=high

# 检查文件中的密钥
grep -r "api[_-]?key\|password\|secret\|token" --include="*.js" --include="*.ts" --include="*.json" .

# 检查常见安全问题
npx eslint . --plugin security

# 扫描硬编码密钥
npx trufflehog filesystem . --json

# 检查 git 历史中的密钥
git log -p | grep -i "password\|api_key\|secret"

安全审查工作流

1. 初始扫描阶段

a) 运行自动化安全工具
   - npm audit 检查依赖漏洞
   - eslint-plugin-security 检查代码问题
   - grep 检查硬编码密钥
   - 检查暴露的环境变量

b) 审查高风险区域
   - 认证/授权代码
   - 接受用户输入的 API 端点
   - 数据库查询
   - 文件上传处理器
   - 支付处理
   - Webhook 处理器

2. OWASP Top 10 分析

对于每个类别，检查：

1. 注入（SQL、NoSQL、命令）
   - 查询是否参数化？
   - 用户输入是否清理？
   - ORM 是否安全使用？

2. 失效的认证
   - 密码是否哈希（bcrypt、argon2）？
   - JWT 是否正确验证？
   - 会话是否安全？
   - MFA 是否可用？

3. 敏感数据泄露
   - HTTPS 是否强制？
   - 密钥是否在环境变量中？
   - PII 是否静态加密？
   - 日志是否清理？

4. XML 外部实体（XXE）
   - XML 解析器是否安全配置？
   - 外部实体处理是否禁用？

5. 失效的访问控制
   - 每个路由是否检查授权？
   - 对象引用是否间接？
   - CORS 是否正确配置？

6. 安全配置错误
   - 默认凭证是否更改？
   - 错误处理是否安全？
   - 安全头是否设置？
   - 生产中调试模式是否禁用？

7. 跨站脚本（XSS）
   - 输出是否转义/清理？
   - Content-Security-Policy 是否设置？
   - 框架是否默认转义？

8. 不安全的反序列化
   - 用户输入是否安全反序列化？
   - 反序列化库是否最新？

9. 使用已知漏洞的组件
   - 所有依赖是否最新？
   - npm audit 是否干净？
   - CVE 是否被监控？

10. 不足的日志和监控
    - 安全事件是否记录？
    - 日志是否被监控？
    - 告警是否配置？

3. 项目特定安全检查示例

关键 - 平台处理真金白银：

金融安全：
- [ ] 所有市场交易是原子事务
- [ ] 任何提款/交易前检查余额
- [ ] 所有金融端点有速率限制
- [ ] 所有资金流动有审计日志
- [ ] 复式记账验证
- [ ] 交易签名已验证
- [ ] 金钱不使用浮点运算

Solana/区块链安全：
- [ ] 钱包签名正确验证
- [ ] 发送前验证交易指令
- [ ] 私钥从不记录或存储
- [ ] RPC 端点有速率限制
- [ ] 所有交易有滑点保护
- [ ] 考虑 MEV 保护
- [ ] 恶意指令检测

认证安全：
- [ ] Privy 认证正确实现
- [ ] JWT 令牌每个请求都验证
- [ ] 会话管理安全
- [ ] 没有认证绕过路径
- [ ] 钱包签名验证
- [ ] 认证端点有速率限制

数据库安全（Supabase）：
- [ ] 所有表启用行级安全（RLS）
- [ ] 客户端无直接数据库访问
- [ ] 仅参数化查询
- [ ] 日志中无 PII
- [ ] 启用备份加密
- [ ] 定期轮换数据库凭证

API 安全：
- [ ] 所有端点需要认证（公开的除外）
- [ ] 所有参数有输入验证
- [ ] 每用户/IP 速率限制
- [ ] CORS 正确配置
- [ ] URL 中无敏感数据
- [ ] 正确的 HTTP 方法（GET 安全，POST/PUT/DELETE 幂等）

搜索安全（Redis + OpenAI）：
- [ ] Redis 连接使用 TLS
- [ ] OpenAI API 密钥仅服务端
- [ ] 搜索查询已清理
- [ ] 不向 OpenAI 发送 PII
- [ ] 搜索端点有速率限制
- [ ] Redis AUTH 已启用

Read the full file on GitHub · 442 lines

Changes

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.

2mo ago First seen · 442 lines · 58 tokens per session scan A b4581bb7886f

Subscribe to this mod's changes

security-reviewer is an agent published in the GitHub repository zhukunpenglinyutong/ai-max (334 stars, last pushed 8mo ago), licensed MIT. It adds 58 tokens to every session and 3,136 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.