security-audit

Name: security-audit
Availability: InStock
Author: wilsto

Audit code for OWASP Top 10 vulnerabilities and generate severity-ranked remediation reports.

Updated Feb 26, 2026

Search Tags:#code review #OWASP #security #vulnerability #audit #DevSecOps

Ready to run

npx skills add https://github.com/wilsto/claude-code-starter-kit --skill security-audit-wilsto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/wilsto/claude-code-starter-kit/tree/main/.claude/skills/security-audit
Command: npx skills add https://github.com/wilsto/claude-code-starter-kit --skill security-audit-wilsto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need to proactively identify and mitigate security vulnerabilities within a codebase, reducing the risk of data breaches and system compromises.

Core Features & Use Cases

Comprehensive Vulnerability Scanning: Analyzes code against OWASP Top 10, identifies dependency risks, checks for exposed secrets, and reviews authentication patterns.
Severity-Ranked Reporting: Provides a clear, prioritized list of findings with actionable remediation steps.
Use Case: Before deploying a new feature, run a security audit to ensure no new vulnerabilities were introduced, especially concerning user input handling and access control.

Quick Start

Run a security audit on the current codebase, focusing on web application vulnerabilities.

Frequently Asked Questions about security-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run a security audit to check my codebase for OWASP Top 10 vulnerabilities?▼

Run a security audit to perform static code analysis across your codebase, scanning for OWASP Top 10 vulnerabilities, exposed secrets, and authentication patterns. It generates a severity-ranked findings report with actionable remediation steps.

Can I scan for exposed secrets and dependency risks in my web applications?▼

Yes, scanning for exposed secrets and dependency risks in web applications is a core feature of the security audit. The analysis identifies these threats and includes them in a severity-ranked findings report with remediation steps.

What's the best way to identify input validation flaws before deploying a new feature?▼

The best way to identify input validation flaws is to run a static code analysis security audit before deployment. This process reviews user input handling and flags vulnerabilities in a prioritized report with specific remediation steps.

Does this static code analysis work for API services and CLI tools, or just full-stack applications?▼

This static code analysis security audit works for API services, CLI tools, web applications, and full-stack applications. It comprehensively reviews authentication patterns and access controls across these diverse environments.

How does a security audit report help with DevSecOps vulnerability remediation?▼

The security audit report aids DevSecOps vulnerability remediation by providing a severity-ranked list of findings. Each identified vulnerability includes actionable remediation steps to directly guide code fixes.

Why should I use static code analysis instead of manual code review for finding security vulnerabilities?▼

Static code analysis proactively identifies security vulnerabilities across the entire codebase, including dependency risks and exposed secrets, faster and more consistently than manual code review. It outputs a prioritized findings report to prevent data breaches.