Attack Path Trace

Name: Attack Path Trace
Author: sodejm

ASecurity

Trace conditional routes from a supplied finding to a user-defined crown jewel in an evidence-linked local graph.

2 stars
0 votes
0 copies
1 view
Added October 15, 2026

security

Security analysis

A100/100

Scanned October 15, 2026

npx -y skills add sodejm/copilot-operation-plugin-for-security --skill attack-path-trace --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Attack Path Trace?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Attack Path Trace

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sodejm-attack-path-trace/badge)](https://www.skillsdirectory.com/skills/sodejm-attack-path-trace)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: attack-path-trace
description: Trace conditional routes from a supplied finding to a user-defined crown jewel in an evidence-linked local graph.
---

# Path tracing

Require a user-defined crown-jewel identifier and an identified starting finding. Use only scoped, time-compatible, typed relationships. A reachable or dependent asset is not automatically controlled. Keep `supported_structural` paths separate from `candidate` paths with missing capabilities or hypothetical relationships. Neither class confirms exploitation.

Use G3 and G4 outputs in the JSON report. Cite every step's evidence ID and source pointer; keep excluded and partial paths with reasons. Do not replace a failed prerequisite with prose or agent judgment. See `docs/gates.md` for path and ranking rules.