threat-modeling

Identify and mitigate STRIDE security threats in system designs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tylern91/dotfiles --skill threat-modeling-tylern91
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: threat-modeling
Source: https://github.com/tylern91/dotfiles/tree/main/agents/.agents/skills/threat-modeling
Command: npx skills add https://github.com/tylern91/dotfiles --skill threat-modeling-tylern91

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Identify and mitigate security threats early in system design using STRIDE to reduce architectural risk and improve defenses.

Core Features & Use Cases

  • STRIDE-based threat identification: Systematically categorize threats across components and trust boundaries.
  • Threat worksheet templates: Reusable templates to capture threats, mitigations, and owners.
  • Risk assessment & mitigation planning: Prioritize remediation with a scoring framework and actionable controls.

Quick Start

Run a threat-modeling session on a new service to identify STRIDE threats and draft mitigations.

Frequently Asked Questions about threat-modeling

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

FAQPage Schema
How do I identify security threats in a system architecture using STRIDE?▼

Threat modeling using STRIDE categorizes threats across components and trust boundaries to identify security risks early in system design. It systematically evaluates spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege vulnerabilities.

What is the best way to document risk assessment and mitigations for architectural reviews?▼

Using structured threat worksheet templates is the best way to document risk assessment and mitigations for architectural reviews. These worksheets capture identified threats, assigned owners, and actionable controls while applying a scoring framework to prioritize remediation.

How do I run a threat modeling session for web-enabled applications?▼

To run a threat modeling session for web-enabled applications, map components and trust boundaries, apply STRIDE to identify threats, and draft practical mitigations. Use reusable worksheets to capture data and score risks for prioritized remediation.

When do I need threat modeling in the software design lifecycle?▼

You need threat modeling early in the software design lifecycle during system design and architectural reviews. Applying STRIDE threat identification before deployment reduces architectural risk and improves defenses across components and trust boundaries.

Does threat modeling support prioritizing security risks across trust boundaries?▼

Yes, threat modeling supports prioritizing security risks across trust boundaries by applying a structured risk scoring framework. This process evaluates identified STRIDE threats and generates actionable controls to prioritize remediation efforts effectively.

What are the limitations of using STRIDE for security design and architecture review?▼

A limitation of using STRIDE for security design is its focus on categorizing threats across components and trust boundaries rather than providing automated exploitation testing. It delivers structured worksheets and risk scoring but requires manual mitigation planning.