stride-analysis-patterns

Use it when:: You're starting a threat model, reviewing a system's architecture or design decisions for security, or preparing for an audit.
STRIDE means:: Six threat categories, each tied to a property: Spoofing (authentication), Tampering (integrity), Repudiation (audit logs), Information disclosure (confidentiality), Denial of service (availability), Elevation of privilege (authorization).
You get:: A threat model document: system overview, data flow diagram, trust boundaries, assets, threats per category with mitigations, a risk matrix and prioritized recommendations.
Also has:: Python templates that model threats and apply STRIDE to a data flow diagram and to each interaction between components.

TL;DR

STRIDE is a checklist for finding threats: for each part of a system, ask whether an attacker could pretend to be someone else, modify data, deny having done something, read data they shouldn't, disrupt availability or gain higher privileges. This skill gives the agent that matrix, each question paired with the family of controls that answers it, and a template for the write-up. The threat model describes the system, draws its data flow, marks trust boundaries, lists assets by sensitivity, tables threats per category with impact, likelihood and mitigations, scores them on a 4-by-4 impact and likelihood matrix, and ends with immediate, 30-day and 90-day recommendations. Python templates model threats, assets and trust boundaries, analyze a data flow diagram, and apply STRIDE per interaction between components. The rules: cover every category, prioritize realistically, involve security, development and operations, keep the model updated, and follow through with mitigations.

Summarizes the skill at 4bde316.

npx skills add https://github.com/wshobson/agents --skill stride-analysis-patterns

skills.sh page Source on GitHub All skills from wshobson/agents

Total Downloads: 22,200 on skills.sh, Nov 9, 2026
Repo stars: 42,334 wshobson/agents
First seen: Jan 20, 2026 on skills.sh

Weekly Downloads

499

-52% over the 8 weeks to Nov 9

Weekly values

Week to	Installs
Sep 21	1,031
Sep 28	1,318
Oct 5	1,325
Oct 12	1,111
Oct 19	932
Oct 26	968
Nov 2	962
Nov 9	499

Category	category:security category:software-engineering Compliance, guardrails, skill vetting and browser fingerprinting. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type	type:guidelines Knowledge and rules the agent applies while it works: best practices, design principles, API references.
Effect	effect:none Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.
Needs	needs:none Instructions only. Works in any agent that supports skills.
Publisher	by:community Everyone else. Unverified vendor claims default to community.
Topics	security architecture

SKILL.md

From wshobson/agents at 4bde316. Checked daily, last changed Nov 6, 2026.

Frontmatter

name: stride-analysis-patterns
description: Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.

STRIDE Analysis Patterns

Systematic threat identification using the STRIDE methodology.

When to Use This Skill

Starting new threat modeling sessions
Analyzing existing system architecture
Reviewing security design decisions
Creating threat documentation
Training teams on threat identification
Compliance and audit preparation

Core Concepts

1. STRIDE Categories

S - Spoofing       → Authentication threats
T - Tampering      → Integrity threats
R - Repudiation    → Non-repudiation threats
I - Information    → Confidentiality threats
    Disclosure
D - Denial of      → Availability threats
    Service
E - Elevation of   → Authorization threats
    Privilege

2. Threat Analysis Matrix

Category	Question	Control Family
Spoofing	Can attacker pretend to be someone else?	Authentication
Tampering	Can attacker modify data in transit/rest?	Integrity
Repudiation	Can attacker deny actions?	Logging/Audit
Info Disclosure	Can attacker access unauthorized data?	Encryption
DoS	Can attacker disrupt availability?	Rate limiting
Elevation	Can attacker gain higher privileges?	Authorization

Templates and detailed worked examples

Full template library lives in references/details.md. Read that file when you need concrete templates for this skill.

Best Practices

Do's

Involve stakeholders - Security, dev, and ops perspectives
Be systematic - Cover all STRIDE categories
Prioritize realistically - Focus on high-impact threats
Update regularly - Threat models are living documents
Use visual aids - DFDs help communication

Don'ts

Don't skip categories - Each reveals different threats
Don't assume security - Question every component
Don't work in isolation - Collaborative modeling is better
Don't ignore low-probability - High-impact threats matter
Don't stop at identification - Follow through with mitigations