Pdlc security
36 slash commands that turn Claude Code into a real PDLC workflow — PRD → TDD → implement → review → ship. Hard contracts force AI to persist artifacts, write failing tests first, and run self-checks. No more "looks done" in chat.
npx -y skills add kanfu-panda/pdlc-skills --skill pdlc-securityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
安全审计
SKILL.md
2.3 KB, 727 tokens by cl100k_base, as published. Nobody here has run it
安全审计
<!-- @include templates/prompts/iron-law.md -->对指定服务或应用进行安全审计，检查常见安全漏洞。
审计范围
-
OWASP Top 10 检查
- SQL 注入
- XSS（跨站脚本）
- CSRF（跨站请求伪造）
- 不安全的直接对象引用
- 安全配置错误
- 敏感数据泄露
- 缺失的访问控制
- 不安全的反序列化
- 使用含已知漏洞的组件
- 日志记录和监控不足
-
认证与授权
- 密码存储方式（是否加盐哈希）
- Token 生成与验证
- 接口权限控制
- 会话管理
-
数据安全
- 敏感信息是否加密存储
- 环境变量中是否有硬编码密钥
- 日志中是否打印敏感数据
- API 响应中是否泄露内部信息
-
依赖安全
- 检查依赖包是否有已知漏洞
- 检查是否使用了过时的库版本
输出格式
⚠️ 必须创建文件，不可仅在对话中输出。
【必须创建文件】 在 docs/07_reviews/code/ 下创建安全审计报告：
- 文件名:
YYYYMMDD-<服务名>-security-audit.md - 文档顶部包含 PDLC 追溯头：
<!-- PDLC-TRACE --> <!-- 功能名称: <服务名> --> <!-- 阶段: 安全审计 --> <!-- 创建时间: <ISO 8601> --> - 按严重程度分级：紧急 / 高危 / 中危 / 低危 / 信息
- 每个问题包含：位置、描述、风险、修复建议、参考链接
- 创建后验证：确认文件已存在于
docs/07_reviews/code/目录 - 在对话中输出报告摘要，但完整报告必须在文件中
要求
<!-- @include templates/prompts/output-language.md -->- 给出具体的代码位置和修复代码示例
- 关键漏洞标注修复优先级
审计目标: $ARGUMENTS
<!-- @include templates/prompts/handoff.md -->本命令的 handoff 输出：
✅ 安全审计报告 完成
📦 产出：docs/04_testing/security/<feature-id>-audit.md
👉 下一步：（本次流程结束，无后续）
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most security skills give in 727 tokens
Counted across 648 of the 828 authors here whose files we hold, read 2026-08-07
- Parameterize all database queriesin 68 of 648, across 51 files
- Hash passwords using bcrypt, scrypt, or argon2in 49 of 648, across 36 files
- Apply rate limiting to authentication endpointsin 48 of 648, across 24 files
- Configure security headersin 35 of 648, across 19 files
- Validate all inputsin 32 of 648, across 24 files
- Validate all external input at the system boundaryin 29 of 648, across 19 files
- Run containers as a non-root userin 28 of 648, across 15 files
- Use httponly secure samesite cookies for sessionsin 26 of 648, across 15 files
- Run dependency audits before every releasein 21 of 648, across 10 files
- Encode output to prevent cross-site scriptingin 21 of 648, across 11 files
- Copy dependencies before source codein 20 of 648, across 9 files
- Store secrets in environment variablesin 20 of 648, across 18 files
Said here and by no other author read
- provide specific code locations and fix examples
- mark priority for critical vulnerabilities
- include a traceability header in the file
- verify the report file exists after creation
- output a report summary in conversation
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.