Threat Modeling logo

Threat Modeling

Community
Omar-Obando
threat-modeling

Use when performing threat modeling, identifying security threats, analyzing attack vectors, creating threat models, and implementing threat mitigation strategies. Includes STRIDE, DREAD, attack trees, and threat modeling frameworks. Based on CISSP, CSSLP certifications and OWASP threat modeling standards.

Overview

PublisherOmar-Obando
Repositoryqwen-orchestrator
Skill namethreat-modeling
Stars
53
Forks
13
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Omar-Obando on GitHub. Read the source before you install it.

Installation

Install the Threat Modeling AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Omar-Obando/qwen-orchestrator/tree/main/skills/threat-modeling
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Omar-Obando/qwen-orchestrator.git /tmp/qwen-orchestrator
mkdir -p .claude/skills
cp -r /tmp/qwen-orchestrator/skills/threat-modeling .claude/skills/threat-modeling
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Threat Modeling in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Threat Modeling on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Threat Modeling is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Threat Modeling Skill — Cybersecurity Engineer

Overview

This skill provides comprehensive guidance for threat modeling and security analysis. It covers threat identification, attack vector analysis, threat model creation, and threat mitigation following CISSP and CSSLP certifications and OWASP threat modeling standards.

When to Use

Use this skill when:

  • Performing threat modeling for systems
  • Identifying security threats and vulnerabilities
  • Analyzing attack vectors and attack paths
  • Creating threat models for applications
  • Implementing STRIDE threat modeling
  • Using DREAD risk assessment
  • Creating attack trees
  • Performing threat modeling workshops
  • Identifying security requirements
  • Creating threat mitigation strategies
  • Documenting threat models
  • Performing threat modeling for APIs
  • Creating threat models for microservices
  • Performing threat modeling for cloud systems
  • Identifying insider threats
  • Analyzing supply chain threats
  • Creating security requirements
  • Performing threat modeling for mobile apps
  • Identifying data flow threats
  • Creating threat models for IoT systems
  • Performing threat modeling for web applications
  • Identifying authentication threats
  • Analyzing authorization threats
  • Creating threat models for databases

Do NOT use this skill when:

  • Writing application business logic (use domain-driven skill)
  • Designing database schemas (use database-design skill)
  • Writing API endpoint specifications (use api-design skill)
  • Performing general code review (use code-review skill)
  • Writing SQL queries (use sql-best-practices skill)
  • Designing multi-page website layouts (use design-system skill)
  • Analyzing deployment configurations (use deployment skill)
  • Writing documentation (use documentation-best-practices skill)

Threat Modeling Frameworks

STRIDE Model

┌─────────────────────────────────────────────────────────────┐
│              STRIDE Threat Modeling                         │
├─────────────────────────────────────────────────────────────┤
│  S - Spoofing Identity:                                     │
│  - Impersonating users or systems                           │
│  - Attack examples: Credential theft, token theft           │
│  - Mitigations: Authentication, MFA, certificates           │
│                                                              │
│  T - Tampering with Data:                                   │
│  - Modifying data in transit or at rest                     │
│  - Attack examples: Data manipulation, code injection       │
│  - Mitigations: Integrity checks, digital signatures        │
│                                                              │
│  R - Repudiation:                                           │
│  - Actions cannot be traced to actor                        │
│  - Attack examples: Denying actions, log tampering          │
│  - Mitigations: Audit logging, non-repudiation              │
│                                                              │
│  I - Information Disclosure:                                │
│  - Unauthorized access to information                       │
│  - Attack examples: Data breaches, eavesdropping            │
│  - Mitigations: Encryption, access controls                 │
│                                                              │
│  D - Denial of Service:                                     │
│  - Service unavailable to legitimate users                  │
│  - Attack examples: DDoS, resource exhaustion               │
│  - Mitigations: Rate limiting, redundancy                   │
│                                                              │
│  E - Elevation of Privilege:                                │
│  - Gaining higher privileges than intended                  │
│  - Attack examples: Privilege escalation, code execution    │
│  - Mitigations: Least privilege, access controls            │
└─────────────────────────────────────────────────────────────┘

DREAD Risk Assessment

┌─────────────────────────────────────────────────────────────┐
│              DREAD Risk Assessment                          │
├─────────────────────────────────────────────────────────────┤
│  D - Damage Potential:                                      │
│  - How much damage can this threat cause?                   │
│  - Scale: 1-10 (1=minor, 10=catastrophic)                   │
│                                                              │
│  R - Reproducibility:                                       │
│  - Can the attack be reproduced consistently?               │
│  - Scale: 1-10 (1=rare, 10=always)                          │
│                                                              │
│  E - Exploitability:                                        │
│  - How easy is it to exploit this threat?                   │
│  - Scale: 1-10 (1=difficult, 10=trivial)                    │
│                                                              │
│  A - Affected Users:                                        │
│  - How many users can be affected?                          │
│  - Scale: 1-10 (1=few, 10=all)                              │
│                                                              │
│  D - Discoverability:                                       │
│  - How easy is it to discover this vulnerability?           │
│  - Scale: 1-10 (1=hard, 10=obvious)                         │
│                                                              │
│  Risk Score = (D + R + E + A + D) / 5                       │
│  - Critical: 8.0+                                           │
│  - High: 6.0-7.9                                            │
│  - Medium: 4.0-5.9                                          │
│  - Low: 0.0-3.9                                             │
└─────────────────────────────────────────────────────────────┘

Threat Modeling Process

Threat Modeling Workflow

┌─────────────────────────────────────────────────────────────┐
│              Threat Modeling Process                        │
├─────────────────────────────────────────────────────────────┤
│  1. Define Scope                                            │
│     - System boundaries                                     │
│  - Assets to protect                                       │
│  - Threat model audience                                   │
│                                                              │
│  2. Identify Assets                                         │
│     - Data in transit                                       │
│  - Data at rest                                            │
│  - Compute resources                                       │
│  - Network boundaries                                      │
│                                                              │
│  3. Identify Threats                                        │
│     - Use STRIDE framework                                  │
│  - Analyze data flow diagrams                              │
│  - Identify attack vectors                                 │
│                                                              │
│  4. Analyze Threats                                         │
│     - Use DREAD assessment                                  │
│  - Prioritize threats                                      │
│  - Document threat details                                 │
│                                                              │
│  5. Mitigate Threats                                        │
│     - Implement security controls                           │
│  - Update threat model                                     │
│  - Document mitigations                                    │
│                                                              │
│  6. Validate                                                │
│     - Review threat model                                   │
│  - Test mitigations                                        │
│  - Update documentation                                    │
└─────────────────────────────────────────────────────────────┘

Data Flow Diagram

┌─────────────────────────────────────────────────────────────┐
│              Data Flow Diagram                              │
├─────────────────────────────────────────────────────────────┤
│  ┌─────────────┐       ┌─────────────┐       ┌───────────┐ │
│  │   Actor     │──────>│   System    │──────>│  Database │ │
│  │  (User)     │       │   (App)     │       │   (DB)    │ │
│  └─────────────┘       └─────────────┘       └───────────┘ │
│         │                      │                     │      │
│         │                      │                     │      │
│         ▼                      ▼                     ▼      │
│  ┌─────────────┐       ┌─────────────┐       ┌───────────┐ │
│  │   External  │       │   Internal  │       │  Storage  │ │
│  │   Services  │       │   Services  │       │   (Data)  │ │
│  └─────────────┘       └─────────────┘       └───────────┘ │
│                                                              │
│  Threats:                                                   │
│  - Spoofing (Actor identity)                                │
│  - Tampering (Data in transit)                              │
│  - Repudiation (Actions not logged)                         │
│  - Information Disclosure (Data at rest)                    │
└─────────────────────────────────────────────────────────────┘

Attack Trees

Attack Tree Structure

┌─────────────────────────────────────────────────────────────┐
│              Attack Tree                                    │
├─────────────────────────────────────────────────────────────┤
│  Root: Gain Admin Access                                    │
│  └── OR:                                                    │
│      ├── AND: Steal Admin Credentials                       │
│      │   ├── Phishing attack                                │
│      │   ├── Keylogger infection                            │
│      │   └── Password reuse                                 │
│      │                                                       │
│      ├── AND: Exploit Vulnerability                         │
│      │   ├── SQL injection                                  │
│      │   ├── XSS attack                                     │
│      │   └── CSRF attack                                    │
│      │                                                       │
│      └── AND: Social Engineering                            │
│          ├── Impersonate admin                              │
│          ├── Bypass MFA                                     │
│          └── Social engineering                             │
│                                                              │
│  Mitigations:                                               │
│  - Multi-factor authentication                              │
│  - Input validation                                         │
│  - Security awareness training                              │
│  - Regular vulnerability scanning                           │
└─────────────────────────────────────────────────────────────┘

Threat Modeling Tools

Threat Modeling Tools

┌─────────────────────────────────────────────────────────────┐
│              Threat Modeling Tools                          │
├─────────────────────────────────────────────────────────────┤
│  OWASP Threat Dragon:                                       │
│  - Open-source threat modeling tool                         │
│  - Draw threat diagrams                                     │
│  - Generate threat lists                                    │
│  - Export threat models                                     │
│                                                              │
│  Microsoft Threat Modeling Tool:                            │
│  - STRIDE-based threat modeling                             │
│  - Template-based approach                                  │
│  - Integration with Azure DevOps                            │
│  - Threat library                                           │
│                                                              │
│  ThreatModeler:                                             │
│  - Cloud-based threat modeling                              │
│  - Automated threat generation                              │
│  - Integration with DevOps tools                            │
│  - Collaborative threat modeling                            │
│                                                              │
│  Custom Tools:                                              │
│  - Excel/Google Sheets templates                            │
│  - Whiteboard sessions                                      │
│  - Documentation-based approach                             │
└─────────────────────────────────────────────────────────────┘

Real-World Impact

Before this skill:

  • No threat modeling
  • Security vulnerabilities discovered late
  • Reactive security approach
  • Incomplete security requirements
  • Security gaps in design

After this skill:

  • Proactive threat identification
  • Security integrated in design
  • Threat-informed decisions
  • Complete security requirements
  • Proven security controls

Cross-References

  • security-auditor - For security audits
  • security-code-review - For code security review
  • devops-pipeline - For security CI/CD gates

References

Frequently asked questions

What does the Threat Modeling AI skill do?

Use when performing threat modeling, identifying security threats, analyzing attack vectors, creating threat models, and implementing threat mitigation strategies. Includes STRIDE, DREAD, attack trees, and threat modeling frameworks. Based on CISSP, CSSLP certifications and OWASP threat modeling standards.

Why use Threat Modeling on TypingMind?

Because you install it once and use it with any model. Threat Modeling is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Threat Modeling in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Omar-Obando/qwen-orchestrator/tree/main/skills/threat-modeling. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Threat Modeling?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Threat Modeling?

As many as you like. As long as a model supports skills, you can use Threat Modeling with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Threat Modeling AI skill free?

Yes. It is published on GitHub by Omar-Obando under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇