security-audit

Scans codebases for OWASP-pattern vulnerabilities and returns a structured severity report.

4|Updated Sep 24, 2025
One-click install
npx skills add https://github.com/alexmond/yj-schema-validator --skill security-audit-alexmond
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/alexmond/yj-schema-validator/tree/main/.claude/skills/security-audit
Command: npx skills add https://github.com/alexmond/yj-schema-validator --skill security-audit-alexmond

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scan code for security vulnerabilities (OWASP patterns, path traversal, injection risks)

Core Features & Use Cases

  • Identify common security issues across codebases
  • Validate input handling, deserialization safety, and secure API usage
  • Use case: Run a security audit on a PR to surface critical vulnerabilities before merge.

Quick Start

Run the security-audit on the repository or a specific file to enumerate vulnerabilities.

Frequently Asked Questions about security-audit

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

FAQPage Schema
How do I scan my codebase for OWASP security vulnerabilities?

Code scanning for OWASP vulnerabilities works by applying pattern checks to repositories or specific directories to identify injection risks, path traversal, and insecure deserialization, returning a structured report with severity levels and remediation suggestions.

Can I run a security audit on a specific file or directory instead of a full repository?

Yes, the security audit can be applied to individual files or specific directories rather than a full repository, allowing targeted detection of path traversal, command injection, and insecure deserialization patterns.

What types of security flaws can a static code analysis tool detect?

Static analysis detects OWASP-pattern flaws including path traversal vulnerabilities, command injection risks, insecure deserialization patterns, and unsafe API usage across your codebase.

How do I integrate vulnerability detection into my CI pipeline before a merge?

Integrate vulnerability detection into CI by running the security audit on pull requests to surface critical vulnerabilities before merge, generating a structured report with locations and remediation suggestions.

Does the security audit report include remediation suggestions for detected vulnerabilities?

Yes, the security audit report includes remediation suggestions alongside severity levels and exact locations for detected vulnerabilities, helping developers resolve path traversal and injection issues.