Threat Modeling
Use when starting a security assessment and you need to map an application's attack surface, enumerate trust boundaries, and rank what to test first — before auditing code or running tools. Produces a prioritized target list.
Install
/plugin marketplace add mn-youssef/security-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add mn-youssef/security-skills --skill threat-modelinggit clone --depth 1 https://github.com/mn-youssef/security-skills.git /tmp/security-skills
mkdir -p ~/.claude/skills
cp -r /tmp/security-skills/skills/threat-modeling ~/.claude/skills/threat-modelingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Threat Modeling (PLAN phase) ## Overview Decide *what to worry about and test first* before spending effort. Map assets, entry points, and trust boundaries; apply STRIDE; rank risks by likelihood × impact. **Core principle:** You can't test everything. Spend effort where a break hurts most. ## Process 1. **Inventory assets** — What's valuable? (user data, money, credentials, PII, admin control, IP) 2. **Map entry points** — Every place untrusted input enters: routes/endpoints, forms, file uploads, query params, headers, webhooks, message queues, mobile API calls, third-party callbacks. 3. **Draw trust boundaries** — Where does data cross from less-trusted to more-trusted? (browser→API, API→DB, service→service, user→admin). Bugs cluster on these lines. 4. **Apply STRIDE** per boundary/component — see `references/stride-and-surface.md`. 5. **Rank** — score each threat: `risk = likelihood × impact` (1–3 each → 1–9). Test high scores first. ## Quick reference — STRIDE | Threat | Question | Defends | |--------|----------|---------| | **S**poofing | Can someone pretend to be another user/service? | Authentication | | **T**ampering | Can data be modified in transit/at rest? | Integrity | | **R**epudiation | Can an action be denied / is it logged? | Non-repudiation | | **I**nformation disclosure | Can data leak? | Confidentiality | | **D**enial of service | Can it be made unavailable? | Availability |
Details
- Skill name
threat-modeling- Repository
- mn-youssef/security-skills
- Path
skills/threat-modeling/SKILL.md- License
- MIT
- Repo updated
- 12 June 2026
FAQ
What does the Threat Modeling skill do?
Use when starting a security assessment and you need to map an application's attack surface, enumerate trust boundaries, and rank what to test first — before auditing code or running tools. Produces a prioritized target list.
How do I install the Threat Modeling skill?
Claude Code plugin: /plugin marketplace add mn-youssef/security-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Threat Modeling popular?
It lives in mn-youssef/security-skills, which has 49 GitHub stars and 7 forks.
Related skills
Access Control Testing
49mn-youssef/security-skills
Use when testing whether users can access data or actions they shouldn't — IDOR/BOLA, horizontal and vertical privilege escalation, multi-tenant isolation, forced browsing, function-level authorization (BFLA), and mass assignment. The #1 cause of real-world breaches.
Active Pentest
49mn-youssef/security-skills
Use when you need to actually run security tests against a running application you own or are authorized to test — the shared execution harness for lab/proxy/scanner setup, safe non-destructive execution, and standardized proof-of-concept capture that the find/exploit specialist skills rely on.
API Security Testing
49mn-youssef/security-skills
Use when testing REST, GraphQL, gRPC, or WebSocket APIs against the OWASP API Security Top 10 — object- and function-level authorization (BOLA/BFLA), excessive data exposure, mass assignment, unrestricted resource consumption, and GraphQL-specific abuse. For apps you own or are authorized to test.
Vulnerability Chaining
49mn-youssef/security-skills
Use when you have multiple findings and need to combine them into realistic end-to-end attack paths — turning several low/medium issues into a single critical-impact exploit chain. The red-team-lead skill that ties the specialists' findings together into business impact.
Securitycards
21Reware-Labs/securitycards
Apply version-specific secure coding guidance to AI-generated or human-written code that uses supported open source libraries. Use when starting a software project, implementing a security-sensitive feature, or reviewing code for secure defaults, authentication, authorization, input handling, injection, cryptography, file handling, network boundaries, secrets, sessions, and other library-specific security concerns.
Security Hierarchy Trace
49dynamics365ninja/d365fo-cli
Trace D365FO security from a Role all the way down to Entry Points, discover which roles reach a given object, or scaffold new security objects (privilege, duty, role, XDS policy). Use when the user asks about permissions, security coverage, roles, duties, privileges, "create a security privilege", "scaffold a security role", "generate a duty", or "create a security policy".
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.