vuln-scan

Scan codebases statically and output VULN-FINDINGS.json and VULN-FINDINGS.md.

5|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/air-gapped/skills --skill vuln-scan-air-gapped
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vuln-scan
Source: https://github.com/air-gapped/skills/tree/main/.claude/skills/vuln-scan
Command: npx skills add https://github.com/air-gapped/skills --skill vuln-scan-air-gapped

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Static vulnerability review of a codebase to identify potential security issues without executing any code, enabling fast risk awareness early in development.

Core Features & Use Cases

  • Static scanning of a target directory with optional THREAT_MODEL.md guidance to surface focus areas (e.g., memory safety, injection, auth).
  • Generates machine-readable VULN-FINDINGS.json and human-readable VULN-FINDINGS.md for ingestion by the /triage workflow and patch teams.
  • Supports focused analysis via --focus and single-pass modes and can append extra context with --extra.

Quick Start

Provide a static review of the target directory, listing candidate vulnerabilities without executing any code.

Frequently Asked Questions about vuln-scan

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

FAQPage Schema
How do I perform a static vulnerability review of a codebase without executing code?

Static vulnerability review scans repository-scale targets to surface potential security issues without executing code. It outputs VULN-FINDINGS.json and VULN-FINDINGS.md files for downstream triage and patch teams.

Can I focus my security audit on specific threat areas like memory safety or injection?

Yes, you can provide optional THREAT_MODEL.md guidance to focus the security audit on specific areas like memory safety, injection, or auth. You can also use --focus and --extra commands to refine the analysis scope.

What is the best way to triage static analysis findings for patch teams?

Generate machine-readable VULN-FINDINGS.json and human-readable VULN-FINDINGS.md files. These outputs support direct ingestion by the /triage workflow, providing structured scoring for patch teams to act upon.

Does the static vulnerability scanner support multi-agent fan-out for large repositories?

Yes, the static vulnerability scanner supports multi-agent fan-out for repository-scale targets. It maintains a read-only review scope and uses a structured scoring workflow suitable for triage ingestion.

What are the limitations of read-only static code review?

Read-only static code review cannot detect runtime vulnerabilities or execute code paths. It enforces a read-only review scope to surface potential issues based on static analysis, requiring downstream triage to confirm actual exploitability.