Threat Modeling Expert

SkillSecurity

Analyzes system designs to find security threats and assess risks using methods like STRIDE.

Available today. Use it from your connected AI after setup.

Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

Then ask your AI: use the Threat Modeling Expert skill

About this skill

Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use PROACTIVELY for security architecture reviews, threat identification, or building secure-by-design systems.

What this skill tells your AI

The instructions your AI receives, as published by davila7/claude-code-templates in cli-tool/components/skills/security/threat-modeling-expert/SKILL.md and read by ahel’s review.

Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use PROACTIVELY for security architecture reviews, threat identification, or building secure-by-design systems.

Capabilities

  • STRIDE threat analysis
  • Attack tree construction
  • Data flow diagram analysis
  • Security requirement extraction
  • Risk prioritization and scoring
  • Mitigation strategy design
  • Security control mapping

Use this skill when

  • Designing new systems or features
  • Reviewing architecture for security gaps
  • Preparing for security audits
  • Identifying attack vectors
  • Prioritizing security investments
  • Creating security documentation
  • Training teams on security thinking

Do not use this skill when

  • You lack scope or authorization for security review
  • You need legal or compliance certification
  • You only need automated scanning without human review

Instructions

  1. Define system scope and trust boundaries
  2. Create data flow diagrams
  3. Identify assets and entry points
  4. Apply STRIDE to each component
  5. Build attack trees for critical paths
  6. Score and prioritize threats
  7. Design mitigations
  8. Document residual risks

Safety

  • Avoid storing sensitive details in threat models without access controls.
  • Keep threat models updated after architecture changes.

Best Practices

  • Involve developers in threat modeling sessions
  • Focus on data flows, not just components
  • Consider insider threats
  • Update threat models with architecture changes
  • Link threats to security requirements
  • Track mitigations to implementation
  • Review regularly, not just at design time

Signals

GitHub stars
32k
Forks
4k
Last commit
Sep 2026
Advanced
Item type
skill
Key
threat-modeling-expert
Source
github.com/davila7/claude-code-templates