stride-analysis-patterns – Security skill for AI agents
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
Install the stride-analysis-patterns skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/stride-analysis-patterns-8a133.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /stride-analysis-patterns – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/stride-analysis-patterns-8a133.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $stride-analysis-patterns – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/stride-analysis-patterns-8a133.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /stride-analysis-patterns – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/stride-analysis-patterns-8a133.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /stride-analysis-patterns – then describe the task you want done.
SKILL.md content
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
Privilege2. 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
Related skills
- wp-mass-recon – Batch WP recon: users, CORS, XMLRPC, leaks across domains.
- digital-forensics – Authorized digital forensics: memory dumps, disk timelines, PCAP investigation, artifact…
- wp-plugin-cve-hunt – Systematic approach to finding and testing CVEs for identified WordPress plugins. Covers…
- wstg-web-pentest – Full WSTG-aligned web application pentest — 12-phase methodology from information…
- procurement-optimizer – Use when running an annual SaaS audit, doing category-level spend review, or…
- xmlrpc-exploitation – Exploit XMLRPC multicall, pingback for brute force and SSRF.
- zimbra-attack – Zimbra SOAP user enum, CVE-2022-37042, SSRF when webmail.
- threat-mitigation-mapping – Map identified threats to appropriate security controls and mitigations. Use when…