attack-path-analysis

Traces validated security findings from source to sink and calibrates severity against a threat model.

Updated May 4, 2026
One-click install
npx skills add https://github.com/antstanley/skills --skill attack-path-analysis-antstanley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: attack-path-analysis
Source: https://github.com/antstanley/skills/tree/main/plugins/security/skills/attack-path-analysis
Command: npx skills add https://github.com/antstanley/skills --skill attack-path-analysis-antstanley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Security scans produce candidate findings, but deciding whether each one is a real, reportable vulnerability requires tracing attacker reachability, trust boundaries, and impact from repository evidence. This Skill turns validated findings into explicit attack-path analyses with calibrated severity and a final reportability decision. ## Core Features & Use Cases - Attack Path Construction: Builds factual attacker stories from repository evidence covering exposure, entry points, identities, trust boundaries, secrets handling, and reachability. - Counterevidence Analysis: Identifies the strongest repository evidence against scoping and reportability fields before finalizing decisions. - Severity Calibration and Policy Adjustment: Applies a mechanical impact/likelihood matrix and suppression rules to produce final severity, priority (P0-P3), and ignore/report decisions. - Use Case: During a repository security scan, a candidate SQL injection finding is validated; this Skill traces whether attacker input actually reaches the sink from an in-scope surface, weighs counterevidence, and decides whether it survives as a reportable high-severity finding. ## Quick Start Ask the agent to run attack-path analysis on the validated findings from the current security scan and produce severity-calibrated reportability decisions.

Frequently Asked Questions about attack-path-analysis

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

FAQPage Schema
How do I analyze whether a security finding is actually exploitable?

Run attack-path analysis on the validated finding to build a factual attacker path from repository evidence, covering exposure, entry points, trust boundaries, and reachability. The Skill then calibrates impact and likelihood and applies a policy matrix to decide reportability.

How is severity calibrated for security scan findings?

Severity is calibrated from repository-evidenced impact and likelihood, then adjusted mechanically with a policy matrix. High and critical ratings require a realistic in-scope attacker path and major security impact, not speculative chains.

When should I use attack-path-analysis instead of a full security scan?

Use it when a scan is already in its attack-path-analysis phase or when you explicitly want to trace a finding from source to sink. It is not the primary trigger for full PR, commit, branch, patch, or repository scans.

What inputs does attack path analysis require?

It requires the per-scan threat model and the validated candidate findings, typically the candidate ledger with rows marked reportable or deferred. If a required input is missing, the workflow stops and asks for it.

Why was my security finding marked as ignore?

Findings are suppressed when evidence shows self-only impact, unachievable preconditions, privileged-only or internal-only paths, or no realistic in-scope attacker reachability. Missing deployment evidence alone does not cause suppression; it lowers confidence instead.