Skip to main content
skill CX Codex

stride-threat-modeling — Claude Code skill: how it works and setup

Run a structured STRIDE threat modeling workshop during system design. The skill maps trust boundaries, catalogs attack vectors per component, and generates backlog tickets.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add securityskills/skills --skill stride-threat-modeling -a claude-code
Open on GitHub

What stride-threat-modeling does

The workshop follows a five-step structure. First, the assistant helps model the system by cataloging processes, stores, data flows, and trust boundaries. Every node gets a number. Boring components like background workers and backup jobs must be included.

Next, every element faces the STRIDE matrix: spoofing, tampering, repudiation, information disclosure, denial of service, and privilege escalation. Threats receive scores based on impact multiplied by likelihood. Remote attacks without authentication take highest priority.

Each identified risk maps to an action: mitigate, transfer, accept with an assigned owner, or redesign to avoid. The final output includes a risk register and work items with clear acceptance criteria. Without updating the model after trust boundary changes or new external dependencies, the analysis quickly becomes obsolete.

What it helps with

  • diagram system architectures with explicit trust boundaries
  • catalog vulnerabilities across components using the STRIDE matrix
  • score and prioritize threats by impact and likelihood
  • turn security mitigations into actionable backlog tickets

Example prompts for the agent

  • Run a STRIDE session for our authentication service and map trust boundaries
  • Threat model the payments API and generate backlog tickets with acceptance criteria
  • Analyze our async worker architecture against the STRIDE threat matrix

How to install stride-threat-modeling

1Skills CLI (Vercel)

npx skills add securityskills/skills --skill stride-threat-modeling -a claude-code

2Manually: put the files in place

~/.claude/skills/stride-threat-modeling/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/stride-threat-modeling/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about stride-threat-modeling

How do I install stride-threat-modeling in Claude Code?

Run npx skills add securityskills/skills --skill stride-threat-modeling -a claude-code in your terminal. You can also place the skill file directly at ~/.claude/skills/stride-threat-modeling/SKILL.md.

What does stride-threat-modeling do?

It guides you through an architectural security review using the STRIDE framework. The skill maps system components, evaluates threats across six attack categories, ranks risks, and produces implementation tickets.

When should you re-evaluate the threat model?

Review the model whenever your architecture introduces new external dependencies, modifies trust boundaries, or introduces new data classifications. Post-incident reviews in production should also feed into future evaluations.

Similar skills

All skills for Security →

From the same set3

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor