PluginBench
Skill
Review
Audit score 70

attack-tree-construction

wshobson/agents

Visualize attack scenarios and defense gaps with systematic threat path mapping.

What is attack-tree-construction?

Build comprehensive attack trees to model how attackers might achieve goals through different paths. Use when planning security architecture, identifying vulnerabilities, communicating risks to stakeholders, or preparing for penetration testing.

  • Model complex attack scenarios with OR/AND logic nodes
  • Attribute attacks with cost, time, skill, and detection likelihood
  • Identify defense gaps and prioritize security investments
  • Visualize dependencies between attack steps
  • Support red team planning and security reviews
  • Communicate threat paths to non-technical stakeholders

How to install attack-tree-construction

npx skills add https://github.com/wshobson/agents --skill attack-tree-construction
Claude Code
Cursor
Windsurf
Cline

How to use attack-tree-construction

  1. 1.Define the root goal (what the attacker wants to achieve)
  2. 2.Identify sub-goals and break them into atomic attack steps
  3. 3.Assign node types: OR (any child succeeds) or AND (all children required)
  4. 4.Add attributes to leaf nodes: cost, time, skill level, detection likelihood
  5. 5.Review with red team or security experts for completeness
  6. 6.Update the tree as new threats emerge or defenses change

Use cases

Good for
  • Planning defensive investments by analyzing attack feasibility and cost
  • Reviewing security architecture to find unexplored attack vectors
  • Preparing penetration test scope by mapping realistic attack paths
  • Communicating security risks to executives with visual threat models
  • Identifying insider threat scenarios alongside external attacks
Who it's for
  • Security architects
  • Penetration testers
  • Risk managers
  • Security engineers
  • Threat analysts

attack-tree-construction FAQ

What's the difference between OR and AND nodes?

OR nodes mean an attacker can achieve the goal through any one of the child paths. AND nodes require all child steps to succeed—useful for modeling dependencies or multi-stage attacks.

How detailed should attack trees be?

Start with high-level goals and expand branches that are most likely or impactful. Avoid over-granularity; leaf nodes should represent atomic, realistic attack steps.

Should I include insider threats?

Yes. Attack trees should model both external and internal threat actors. Insider paths often have lower skill/cost requirements and higher success rates.

How often should I update attack trees?

Review quarterly or when significant changes occur: new technologies, architecture changes, or emerging threat intelligence.

Can attack trees help with compliance?

Yes. They demonstrate systematic threat analysis and risk-based defense planning, supporting security governance and audit requirements.

Full instructions (SKILL.md)

Source of truth, from wshobson/agents.


name: attack-tree-construction description: Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.

Attack Tree Construction

Systematic attack path visualization and analysis.

When to Use This Skill

  • Visualizing complex attack scenarios
  • Identifying defense gaps and priorities
  • Communicating risks to stakeholders
  • Planning defensive investments
  • Penetration test planning
  • Security architecture review

Core Concepts

1. Attack Tree Structure

                    [Root Goal]
                         |
            ┌────────────┴────────────┐
            │                         │
       [Sub-goal 1]              [Sub-goal 2]
       (OR node)                 (AND node)
            │                         │
      ┌─────┴─────┐             ┌─────┴─────┐
      │           │             │           │
   [Attack]   [Attack]      [Attack]   [Attack]
    (leaf)     (leaf)        (leaf)     (leaf)

2. Node Types

TypeSymbolDescription
OROvalAny child achieves goal
ANDRectangleAll children required
LeafBoxAtomic attack step

3. Attack Attributes

AttributeDescriptionValues
CostResources needed$, $$, $$$
TimeDuration to executeHours, Days, Weeks
SkillExpertise requiredLow, Medium, High
DetectionLikelihood of detectionLow, Medium, High

Templates and detailed worked examples

Full template library lives in references/details.md. Read that file when you need concrete templates for this skill.

Best Practices

Do's

  • Start with clear goals - Define what attacker wants
  • Be exhaustive - Consider all attack vectors
  • Attribute attacks - Cost, skill, and detection
  • Update regularly - New threats emerge
  • Validate with experts - Red team review

Don'ts

  • Don't oversimplify - Real attacks are complex
  • Don't ignore dependencies - AND nodes matter
  • Don't forget insider threats - Not all attackers are external
  • Don't skip mitigations - Trees are for defense planning
  • Don't make it static - Threat landscape evolves