vulnerability-validation

Validate commit-security-scan findings for exploitability and output validated-findings.json.

Updated Feb 3, 2026

Search Tags:#proof-of-concept #validate #cvss #threat-model #exploitability #security-findings

Ready to run

npx skills add https://github.com/IEatCodeDaily/cli-dotfiles --skill vulnerability-validation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vulnerability-validation
Source: https://github.com/IEatCodeDaily/cli-dotfiles/tree/main/configs/claude-code/skills/vulnerability-validation
Command: npx skills add https://github.com/IEatCodeDaily/cli-dotfiles --skill vulnerability-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps security teams confirm which findings from commit-security-scan are genuinely exploitable, reducing noise and guiding effective remediation.

Core Features & Use Cases

Exploitability assessment: evaluate each finding's reachability and impact within the codebase.
Mitigation & PoC guidance: provide actionable steps and evidence-backed remediation paths (including PoC references) for real issues.
Audit-ready outputs: generate validated-findings.json with statuses, exploitability paths, and CVSS scores.

Quick Start

After running commit-security-scan, use this skill to validate findings and produce validated-findings.json with the combined analysis.

Frequently Asked Questions about vulnerability-validation

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

FAQPage Schema

How do I validate security findings to determine actual exploitability after a code scan?▼

To validate security findings for exploitability, you need a threat-model.md and a security-findings.json file. The process evaluates each finding's reachability and impact, outputting a validated-findings.json with statuses and CVSS scores.

What is the best way to reduce false positives from high and critical security scans?▼

The best way to reduce false positives is to perform a threat-model-guided review of high and critical findings. This assesses actual exploitability paths within the codebase, filtering noise and producing audit-ready validated results.

Do I need a threat model to validate exploitability and generate remediation guidance?▼

Yes, a threat model is required. You must place a threat-model.md file at .factory/threat-model.md to guide the exploitability assessment and generate accurate mitigation and proof-of-concept guidance.

Can I filter security findings by severity or specific finding IDs during validation?▼

Yes, you can filter security findings by severity or specific finding IDs. The validation process accepts optional inputs for finding IDs and severity filters to focus the exploitability analysis on targeted subsets.

How does proof-of-concept guidance work for confirmed exploitable vulnerabilities?▼

Proof-of-concept guidance provides actionable steps and evidence-backed remediation paths for confirmed exploitable vulnerabilities. It references PoC steps directly within the validated-findings.json output for audit readiness.

What format does the validated security findings output use for audit readiness?▼

The validated security findings output uses the validated-findings.json format. It contains validation statuses, exploitability paths, and CVSS scores to provide audit-ready documentation for confirmed issues.