mcpField
S
security-audit

security-audit

github.com/89jobrienSecurity447 installsUpdated 9w ago
Repository

About security-audit

security-audit is a security auditing skill for teams reviewing code and systems before release or during incident and compliance work. It covers vulnerability analysis through findings and remediation planning, with severity, CVSS, and CWE details.

Key features

  1. 01Security code reviews
  2. 02Vulnerability identification with CVSS
  3. 03OWASP Top 10 assessments
  4. 04Authentication and authorization audits
  5. 05Dependency vulnerability analysis
  6. 06Remediation roadmaps

Use cases

  1. 01Reviewing code before release
  2. 02Preparing for compliance audits
  3. 03Preparing for penetration tests
  4. 04Assessing dependencies for vulnerabilities

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/89jobrien/steve --skill security-audit

After installing, type/security-auditin Claude Code to confirm it loaded.

Bundled filesreferences/owasp-checklist.mdreferences/security-audit.template.md

Details

From the project README

Security Audit Skill

Comprehensive security auditing covering code review, vulnerability assessment, OWASP Top 10, dependency analysis, and remediation planning.

What This Skill Does

  • Conducts security code reviews
  • Identifies vulnerabilities (CVSS scoring)
  • Performs OWASP Top 10 assessments
  • Audits authentication/authorization
  • Reviews data protection controls
  • Analyzes dependency vulnerabilities
  • Creates remediation roadmaps

When to Use

  • Security reviews before release
  • Compliance audits
  • Penetration test preparation
  • Incident response analysis
  • Dependency vulnerability assessment

Reference Files

  • references/SECURITY_AUDIT.template.md - Comprehensive security audit report format
  • references/owasp_checklist.md - OWASP Top 10 checklist with CVSS scoring and CWE references

Workflow

  1. Define scope and methodology
  2. Perform static/dynamic analysis
  3. Document findings by severity
  4. Map to OWASP categories
  5. Create remediation roadmap
  6. Verify fixes

Output Format

Security findings should include:

  • Severity (Critical/High/Medium/Low)
  • CVSS score and vector
  • CWE classification
  • Proof of concept
  • Remediation steps

Comments

Markdown supported