Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add HermeticOrmus/LibreSecOps-Claude-Code --skill attack-treesgit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/attack-trees)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/attack-trees"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/attack-trees/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/attack-trees"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/attack-trees.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00046 | $0.02802 |
| Opus 5.5 | $0.00018 | $0.01121 |
| Sonnet 5.5 | $0.00009 | $0.00560 |
| Haiku 4.5 | $0.00005 | $0.00280 |
Grade A, and why
attack-trees scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Attack Trees
Attack tree construction methodology, notation, common patterns, and analysis techniques for decomposing complex threats into specific, analyzable attack paths.
Knowledge Base
What Are Attack Trees?
Attack trees are hierarchical diagrams that model the different ways an attacker can achieve a specific objective. The root node is the attacker's goal, intermediate nodes are subgoals, and leaf nodes are specific, atomic actions the attacker takes. Nodes are connected by AND gates (all children must succeed) or OR gates (any child is sufficient).
Attack trees were formalized by Bruce Schneier (1999) and remain one of the most practical tools for understanding and communicating about security threats.
Tree Notation
Text-based notation (used in this plugin):
[ROOT GOAL] (OR) # Attacker wants to achieve this
├── [Subgoal A] (AND) # Approach A requires all steps
│ ├── [Action A.1] {leaf} # Specific atomic action
│ └── [Action A.2] {leaf} # Both A.1 AND A.2 needed
├── [Subgoal B] (OR) # Approach B has alternatives
│ ├── [Action B.1] {leaf} # B.1 alone is sufficient
│ └── [Action B.2] {leaf} # OR B.2 alone is sufficient
└── [Subgoal C] {leaf} # Sometimes a single action is enough
Node annotations:
[Action] {leaf}
Cost: $ / $$ / $$$ / $$$$ / $$$$$ # Resources attacker needs to spend
Skill: Novice / Intermediate / Expert # Required attacker skill level
Time: Minutes / Hours / Days / Weeks # Time to execute
Detect: Low / Medium / High # Probability of detection
Control: [Name] or NONE # Existing security control
ATT&CK: T[xxxx] # MITRE ATT&CK technique ID
Common Attack Tree Templates
Account Takeover
[Take Over User Account] (OR)
├── [Steal Credentials] (OR)
│ ├── [Phishing] (AND)
│ │ ├── [Send convincing phishing email] {leaf}
│ │ │ Cost: $, Skill: Novice, Time: Hours, Detect: Medium
│ │ └── [Victim enters credentials on fake page] {leaf}
│ │ Cost: $, Skill: N/A (victim action), Detect: Low
│ ├── [Credential Stuffing] (AND)
│ │ ├── [Obtain leaked credential database] {leaf}
│ │ │ Cost: $, Skill: Novice, Time: Minutes, Detect: Low
│ │ └── [Automate login attempts] {leaf}
│ │ Cost: $, Skill: Novice, Time: Hours, Detect: High
│ │ Control: Rate limiting, account lockout
│ ├── [Keylogger/Malware] (AND)
│ │ ├── [Deliver malware to victim device] {leaf}
│ │ │ Cost: $$, Skill: Intermediate, Time: Days, Detect: Medium
│ │ └── [Capture credentials from keystrokes] {leaf}
│ │ Cost: $, Skill: Intermediate, Time: Hours, Detect: Low
│ └── [Network Sniffing] (AND)
│ ├── [Position on victim's network] {leaf}
│ │ Cost: $$, Skill: Intermediate, Time: Hours, Detect: Low
│ └── [Intercept cleartext credentials] {leaf}
│ Cost: $, Skill: Intermediate, Time: Minutes, Detect: Low
│ Control: TLS encryption
├── [Exploit Authentication Weakness] (OR)
│ ├── [Brute Force Weak Password] {leaf}
│ │ Cost: $, Skill: Novice, Time: Hours, Detect: High
│ │ Control: Password policy, rate limiting
│ ├── [Exploit Password Reset Flow] (AND)
│ │ ├── [Discover user's email address] {leaf}
│ │ └── [Exploit weak reset token generation] {leaf}
│ │ Control: Cryptographic random tokens
│ └── [Session Hijacking via XSS] (AND)
│ ├── [Find XSS vulnerability] {leaf}
│ │ Cost: $$, Skill: Intermediate, Time: Hours, Detect: Low
│ └── [Steal session cookie] {leaf}
│ Cost: $, Skill: Intermediate, Time: Minutes, Detect: Low
│ Control: HttpOnly cookies, CSP
├── [Bypass MFA] (OR)
│ ├── [SIM Swap (SMS-based MFA)] {leaf}
│ │ Cost: $$, Skill: Intermediate, Time: Days, Detect: Medium
│ ├── [Real-time Phishing Proxy (evilginx2)] {leaf}
│ │ Cost: $$, Skill: Expert, Time: Hours, Detect: Medium
│ └── [Social Engineer Help Desk] {leaf}
│ Cost: $, Skill: Intermediate, Time: Hours, Detect: Medium
│ Control: Identity verification procedures
└── [Insider Access] (OR)
├── [Malicious Administrator] {leaf}
│ Cost: $, Skill: Novice, Time: Minutes, Detect: Medium
│ Control: Audit logging, least privilege, separation of duties
└── [Bribe/Coerce Employee] {leaf}
Cost: $$$, Skill: Novice, Time: Days, Detect: Low
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago Changed · +5 lines · +46 tokens per session 5dda8f7d4a54
- 1mo ago First seen · 219 lines · 0 tokens per session scan A f45de879f217
attack-trees is a skill published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 46 tokens to every session and 2,802 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
implementing-devsecops-security-scanning
Integrates Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Software Composition Analysis (SCA) into CI/CD pipelines using open-source tools. Covers Semgrep for SAST, Trivy for SCA and container scanning, OWASP ZAP for DAST, and Gitleaks for secrets detection. Activates for…
building-devsecops-pipeline-with-gitlab-ci
Design and implement a comprehensive DevSecOps pipeline in GitLab CI/CD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
implementing-runtime-application-self-protection
Deploy Runtime Application Self-Protection (RASP) agents to detect and block attacks from within application runtime, covering OpenRASP integration, attack pattern detection, and security policy configuration for Java and Python web applications.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
audit-production-readiness
Audit a repository or service for release-blocking bugs, security, data/privacy, AI-agent, supply-chain, operability, and scale risks. Use for deep code audits, threat models, pre-production reviews, vulnerability triage, incidents, defensive investigation, release gates, or evidence-based 10k-to-1M-user readiness.