STRIDE Analysis Patterns
SkillDocs & knowledgeThis skill applies STRIDE threat modeling to a system so an AI agent can identify security threats in a structured way. It walks through six categories: spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege. For each category it asks whether an attacker could exploit that weakness and which controls, such as authentication or encryption, address it. It is used when analyzing system security, running threat modeling sessions, or writing security documentation.
Then ask your AI: use the STRIDE Analysis Patterns skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Have a description or diagram of the system you want to analyze.
What your AI can do with it
- Work through all six STRIDE categories for a system
- Ask whether an attacker could exploit each weakness
- Map each category to a control family like authentication
- Provide templates and worked examples for threat modeling
- Follow threats through to mitigations
Getting started
- Have a description or diagram of the system you want to analyze.
- Add the skill to your agent's available skills.
- Ask the agent to run a STRIDE analysis on the system.
- Review the threats and controls the agent lists for each category.
- Read the references file when you need concrete templates.
What this skill tells your AI
The instructions your AI receives, as published by wshobson/agents in plugins/security-scanning/skills/stride-analysis-patterns/SKILL.md and read by Ahel’s review.
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
Signals
- GitHub stars
- 40k
- Forks
- 4k
- Last commit
- Oct 2026
Questions
- What does the skill do?
- It guides an agent through STRIDE threat modeling, checking a system against six categories and asking whether an attacker could exploit each weakness and which controls address it.
- When should I use it?
- Use it when starting threat modeling sessions, analyzing existing architecture, reviewing security design decisions, creating threat documentation, training teams, or preparing for compliance and audits.
- Does it cover every STRIDE category?
- Yes. It advises covering all six categories, since each reveals different threats, and warns against skipping any of them.
Advanced
- Item type
- skill
- Key
stride-analysis-patterns-wshobson- Source
- github.com/wshobson/agents
Related picks
Skill · mattpocock
The pick for TypeScripttypescript-providers
Skill · composiohq
The pick for TypeScripttechstack-infra
Skill · transilienceai
The pick for Infrainfra-as-code-review
Skill · mohitagw15856
The pick for Infratesting-api-security-with-owasp-top-10
Skill · mukul975
The pick for Web (OWASP)checking-owasp-compliance
Skill · jeremylongshore
The pick for Web (OWASP)