skills.rest
robotijn
robotijnCOMMUNITY
Explore all skills by this author →
GitHub

threat-modeler

Decompose application architecture threats using STRIDE, PASTA, LINDDUN, and MITRE ATT&CK.

3|2|Updated Jan 23, 2026
Search Tags:#threat modeling#STRIDE#security architecture#GDPR compliance#MITRE ATT&CK#pre-code security#LINDDUN
One-click install
npx skills add https://github.com/robotijn/ctoc --skill threat-modeler-robotijn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: threat-modeler
Source: https://github.com/robotijn/ctoc/tree/main/skills/security/threat-modeler
Command: npx skills add https://github.com/robotijn/ctoc --skill threat-modeler-robotijn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reactive security tools like SAST scanners only find vulnerabilities after code is written, leaving design-class flaws (missing trust boundaries, authorization confusion, privacy leaks by aggregation) undetected until production. This skill fills that gap by performing threat decomposition at the architecture and design phase, before any code is committed, preventing costly retrofits later.

Core Features & Use Cases

  • Multi-methodology support: Applies STRIDE for security threats, LINDDUN for privacy threats, PASTA for risk-centric business justification, attack trees for high-value asset analysis, and MITRE ATT&CK/ATLAS tagging for canonical attacker technique mapping.
  • Version-controlled threat models: Produces machine-readable, repo-stored threat models instead of rotting wiki documents, enabling diff review, CI integration, and full lifecycle tracking.
  • Compliance alignment: Automatically maps threats to CRA Article 13, GDPR Article 25, and other regulatory requirements, with built-in checks for missing privacy analysis, unsigned risk acceptances, and stale models.
  • Use Case: For a new EU-facing SaaS processing user health data, run this skill during initial architecture design to identify all STRIDE security threats, LINDDUN privacy threats, and required ATLAS tags for any integrated LLM features before writing any backend code.

Quick Start

Use the threat-modeler skill to perform a full STRIDE, LINDDUN, and MITRE ATT&CK/ATLAS analysis on your new patient portal architecture before writing any backend code.

Frequently Asked Questions about threat-modeler

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify security threats before writing any application code?▼

Design-time threat decomposition identifies security and privacy vulnerabilities by applying STRIDE and LINDDUN methodologies to architecture diagrams before application code is written. This process catches missing trust boundaries and authorization flaws early, preventing costly production retrofits.

Can I map data-flow diagram threats to GDPR Article 25 compliance requirements?▼

Yes, threat modeling maps identified threats to GDPR Article 25 and CRA Article 13 regulatory requirements. It analyzes data-flow diagrams to detect privacy leaks by aggregation and automatically generates compliance alignment checks for EU market requirements.

What is the best way to perform threat modeling for AI-integrated SaaS applications?▼

Applying STRIDE for security threats, LINDDUN for privacy threats, and MITRE ATT&CK/ATLAS tagging to architecture diagrams is the best way to threat model AI-integrated SaaS. This catches design vulnerabilities and required ATLAS tags for integrated LLM features before backend development.

How do I generate machine-readable threat models for CI integration?▼

Version-controlled threat models are produced as machine-readable, repo-stored files instead of wiki documents. This output enables diff review, CI integration, and full lifecycle tracking by assigning owners, mitigation statuses, and regulatory compliance mappings.

Does design-time threat decomposition work with PASTA and attack tree methodologies?▼

Yes, threat decomposition supports PASTA for risk-centric business justification and attack trees for high-value asset analysis. It applies these alongside STRIDE and LINDDUN to architecture diagrams and system design documents for SaaS, web, and AI-integrated applications.

Why should I run threat modeling during the architecture design phase instead of using SAST scanners?▼

Reactive SAST scanners only find vulnerabilities after code is written, leaving design-class flaws undetected until production. Running threat modeling during architecture design prevents costly retrofits by identifying missing trust boundaries and privacy leaks before any code is committed.

Related Skills

Explore More Software Engineering Skills→
MacPhobosMacPhobos

Threat Modeling (STRIDE)

Create data flow diagrams, threat registers, and mitigation plans using STRIDE.

Community
Advanced
abnejsolutions-altabnejsolutions-alt

fedramp-20x-expert

Automate FedRAMP 20X modernization guidance for security program owners.

Community
Advanced
harnessharness
80

configure-repo-scan

Insert code scanning steps into existing Harness pipeline YAML.

Official
Intermediate
Division6066Division6066

stride-analysis-patterns

Identify STRIDE threats and patterns for structured threat modeling sessions.

Community
Advanced