Skip to content
Back to skills

Threat Model

ASecurity

Conduct STRIDE-based threat modeling for system components and data flows

  • 57 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 17, 2026
securityrustgoapisecurity

Works with

  • api

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add diegosouzapw/awesome-omni-skill --skill threat-model --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Threat Model?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Threat Model
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/diegosouzapw-threat-model-awesome-omni-skill/badge)](https://www.skillsdirectory.com/skills/diegosouzapw-threat-model-awesome-omni-skill)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: Threat Model
description: Conduct STRIDE-based threat modeling for system components and data flows
category: security
version: 1.0.0
triggers:
  - ingress-point-added
  - auth-changes
  - security-assessment
globs: "**/api/**,**/auth/**,**/security/**"
---

# Threat Model Skill

Conduct STRIDE-based threat modeling for system components and data flows.

## Trigger Conditions
- New ingress points are added (APIs, webhooks, queue consumers)
- Authentication or authorization changes are made
- User invokes with "threat model" or "security assessment"

## Input Contract
- **Required:** System or component to model
- **Required:** Data flow diagram or description
- **Optional:** Trust boundaries, existing security controls

## Output Contract
- STRIDE analysis per component
- Risk matrix (likelihood × impact)
- Prioritized mitigation recommendations
- Attack tree for highest-risk threats

## Tool Permissions
- **Read:** All source code, config files, API specs, network policies
- **Write:** `docs/security/` directory
- **Search:** Codebase for security-relevant patterns

## Execution Steps
1. Map the system's data flow diagram
2. Identify trust boundaries
3. Apply STRIDE to each component crossing a trust boundary
4. Assess likelihood and impact for each threat
5. Prioritize threats by risk score
6. Recommend mitigations for top threats
7. Document in threat model report

## Success Criteria
- Every ingress point has been analyzed
- STRIDE applied to all trust boundary crossings
- Risk matrix populated with scores
- Top 5 threats have concrete mitigation recommendations

## Escalation Rules
- Escalate if a Critical-severity threat is identified
- Escalate if existing controls are insufficient for a High-risk threat
- Escalate if the threat requires infrastructure-level changes

## Example Invocations

**Input:** "Threat model the new webhook ingestion endpoint"

**Output:** STRIDE analysis: Spoofing (no HMAC verification — HIGH), Tampering (no request body signing — MEDIUM), Repudiation (no audit log — MEDIUM), Information Disclosure (error messages leak internals — LOW), DoS (no rate limiting — HIGH), EoP (webhook can trigger admin actions — CRITICAL). Mitigation plan prioritized.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.