vulnerability-validation

Validate security findings by assessing exploitability and generating proof-of-concept exploits.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/lucking7/factory-plugins --skill vulnerability-validation-lucking7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vulnerability-validation
Source: https://github.com/lucking7/factory-plugins/tree/main/plugins/security-engineer/skills/vulnerability-validation
Command: npx skills add https://github.com/lucking7/factory-plugins --skill vulnerability-validation-lucking7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the validation of security findings by providing a structured process to confirm real vulnerabilities, filter false positives, and produce actionable PoCs for security teams.

Core Features & Use Cases

  • Threat-model-driven validation: Align findings with the system context to assess reachability and exploitability.
  • Proof-of-Concept generation: Create minimal PoCs to demonstrate exploitation safely.
  • Decision guidance: Classify findings (CONFIRMED, LIKELY, FALSE_POSITIVE, NEEDS_MANUAL_REVIEW) and document mitigations and remediation steps.
  • Use Case: After a commit-security-scan identifies suspicious findings, run vulnerability-validation to verify which findings require remediation and produce PoCs for those that are real.

Quick Start

Run vulnerability-validation on the latest security-findings.json with the default threat model at .factory/threat-model.md.

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 and filter false positives from a code scan?

You validate security findings by assessing exploitability and filtering false positives against a system threat model. This workflow classifies results as CONFIRMED, LIKELY, FALSE_POSITIVE, or NEEDS_MANUAL_REVIEW to prioritize remediation.

How can I generate a proof-of-concept exploit for detected vulnerabilities?

You can generate a proof-of-concept exploit by validating HIGH or CRITICAL findings within their specific threat model context. This approach creates minimal PoCs to safely demonstrate exploitation and guide immediate remediation decisions.

What is threat-model-driven vulnerability validation and when do I need it?

Threat-model-driven vulnerability validation is the process of assessing security findings against system context to evaluate reachability and exploitability. You need it after running a security scan to verify which suspicious findings require actual remediation.

Can I assess exploitability for specific CVSS severity levels like HIGH or CRITICAL?

Yes, you can assess exploitability for specific CVSS severity levels by applying severity filters to your security findings. This workflow prioritizes HIGH and CRITICAL findings to focus validation efforts on the most pressing risks.

Do I need a threat model file to validate security findings?

Yes, you need a threat model file at .factory/threat-model.md and a security-findings.json file from a commit security scan. These inputs provide the necessary system context and raw vulnerability data required for accurate validation.