agentsclimarketplace

Pdlc security

Skill kanfu-panda/pdlc-skills/skills/pdlc-security

安全审计From its SKILL.md

Install
npx -y skills add kanfu-panda/pdlc-skills --skill pdlc-security

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 10 stars10 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.

SKILL.md

2.3 KB, 727 tokens by cl100k_base, as published. Nobody here has run it

安全审计

<!-- @include templates/prompts/iron-law.md -->

对指定服务或应用进行安全审计,检查常见安全漏洞。

审计范围

  1. OWASP Top 10 检查

    • SQL 注入
    • XSS(跨站脚本)
    • CSRF(跨站请求伪造)
    • 不安全的直接对象引用
    • 安全配置错误
    • 敏感数据泄露
    • 缺失的访问控制
    • 不安全的反序列化
    • 使用含已知漏洞的组件
    • 日志记录和监控不足
  2. 认证与授权

    • 密码存储方式(是否加盐哈希)
    • Token 生成与验证
    • 接口权限控制
    • 会话管理
  3. 数据安全

    • 敏感信息是否加密存储
    • 环境变量中是否有硬编码密钥
    • 日志中是否打印敏感数据
    • API 响应中是否泄露内部信息
  4. 依赖安全

    • 检查依赖包是否有已知漏洞
    • 检查是否使用了过时的库版本

输出格式

⚠️ 必须创建文件,不可仅在对话中输出。

【必须创建文件】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 1 of the 12 instructions most security skills give in 727 tokens

Counted across 666 of the 889 authors here whose files we hold, read 2026-09-06

  • Use parameterized queries for database accessin 82 of 666, across 79 files
  • Hash passwords with BCryptin 55 of 666, across 39 files
  • Implement rate limiting for public endpointsin 48 of 666, across 34 files
  • Use environment variables for secretsin 35 of 666
  • Scan dependencies for vulnerabilitieshere, and in 35 of 666, across 24 files
  • Validate and sanitize all user inputin 35 of 666, across 32 files
  • Add security headers to all responsesin 34 of 666, across 20 files
  • Validate all external input at the system boundaryin 26 of 666, across 25 files
  • Use parameterized queries to prevent SQL injectionin 25 of 666, across 13 files
  • Store secrets in Vault or environment variablesin 25 of 666, across 10 files
  • Run containers as a non-root userin 21 of 666, across 18 files
  • Validate all input using Bean Validationin 19 of 666, across 5 files

Said here and by no other author read

  • Inspect data encryption and storage practices
  • Include PDLC trace header in report
  • Provide code location and fix examples
  • Verify file existence after creation

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.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.