Individual skill

kill-chain-analysis

Kill chain analysis and attack path decision-making — findings analysis, attack vector selection, target prioritization, causal prerequisites and evidence confidence.

packages/decepticon/decepticon/skills/standard/decepticon/kill-chain-analysis/SKILL.md

Read pinned source

Source commit cc6044561ff32188dc0aa899bcc7d3666ffcfd1c

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 2, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 6,563
Repository last updated: Nov 7, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent Repository topic
ai Repository topic
cybersecurity Repository topic
hacking Repository topic
langchain Repository topic
langgraph Repository topic
llm Repository topic
generative-ai Repository topic
pentesting Repository topic
pentest Repository topic
engineering Derived category

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 2,734 bytes

Read excerpt


# Causal attack-path analysis

An attack path is a hypothesis about compatible security primitives, not a list of
technique names. Each link needs an input/precondition, resulting capability,
identity, target, state and evidence. A prior primitive must actually supply what
the next consumes in the same relevant environment. Different tenants, expired
tokens, incompatible privileges or unproven reachability can break an apparent chain.

## Evidence and counterexamples

Mark links observed, independently reproduced, inferred or contradicted. Keep the
supporting artifact and a competing benign explanation. Scanner hits, topology
edges, apparent secrets and service versions are leads rather than proven transitions.
An observed access boundary does not establish a bypass. A plausible destructive