agentleFS
Sign inStart free
GhostekenGhosteken/agent-harness/skills/attack-tree-construction/SKILL.md

attack-tree-construction

Skill2 starsChanged 42 days agoMITView on GitHub

Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.

5 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If detailed templates are required, open resources/implementation-playbook.md.

    line 31
  2. Distinctive:

    Avoid including sensitive exploit details unless required.

    line 36
  3. Distinctive:

    Use this skill only when the task clearly matches the scope described above.

    line 43
  4. Distinctive:

    Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

    line 44
  5. Distinctive:

    Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

AUTHORIZED USE ONLY: Use this skill only for authorized security assessments, defensive validation, or controlled educational environments.

Attack Tree Construction

Systematic attack path visualization and analysis.

Use this skill when

  • Visualizing complex attack scenarios
  • Identifying defense gaps and priorities
  • Communicating risks to stakeholders
  • Planning defensive investments or test scopes

Do not use this skill when

  • You lack authorization or a defined scope to model the system
  • The task is a general risk review without attack-path modeling
  • The request is unrelated to security assessment or design

Instructions

  • Confirm scope, assets, and the attacker goal for the root node.
  • Decompose into sub-goals with AND/OR structure.
  • Annotate leaves with cost, skill, time, and detectability.
  • Map mitigations per branch and prioritize high-impact paths.
  • If detailed templates are required, open resources/implementation-playbook.md.

Safety

  • Share attack trees only with authorized stakeholders.
  • Avoid including sensitive exploit details unless required.

Resources

  • resources/implementation-playbook.md for detailed patterns, templates, and examples.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free