
Threat Modeling Expert
- 27 installs
- 1.2k repo stars
- Updated August 2, 2026
- rmyndharis/antigravity-skills
Helps with ai & agent building tasks during AI-assisted development.
About
threat-modeling-expert is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.
- threat-modeling-expert
- AI & Agent Building
- AI-coding skill
Threat Modeling Expert by the numbers
- 27 all-time installs (skills.sh)
- +3 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #9,601 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/rmyndharis/antigravity-skills --skill threat-modeling-expertAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 27 |
|---|---|
| repo stars | ★ 1.2k |
| Last updated | August 2, 2026 |
| Repository | rmyndharis/antigravity-skills ↗ |
What it does
Helps with ai & agent building tasks during AI-assisted development.
Files
Threat Modeling Expert
Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use PROACTIVELY for security architecture reviews, threat identification, or building secure-by-design systems.
Capabilities
- STRIDE threat analysis
- Attack tree construction
- Data flow diagram analysis
- Security requirement extraction
- Risk prioritization and scoring
- Mitigation strategy design
- Security control mapping
Use this skill when
- Designing new systems or features
- Reviewing architecture for security gaps
- Preparing for security audits
- Identifying attack vectors
- Prioritizing security investments
- Creating security documentation
- Training teams on security thinking
Do not use this skill when
- You lack scope or authorization for security review
- You need legal or compliance certification
- You only need automated scanning without human review
Instructions
1. Define system scope and trust boundaries 2. Create data flow diagrams 3. Identify assets and entry points 4. Apply STRIDE to each component 5. Build attack trees for critical paths 6. Score and prioritize threats 7. Design mitigations 8. Document residual risks
Safety
- Avoid storing sensitive details in threat models without access controls.
- Keep threat models updated after architecture changes.
Best Practices
- Involve developers in threat modeling sessions
- Focus on data flows, not just components
- Consider insider threats
- Update threat models with architecture changes
- Link threats to security requirements
- Track mitigations to implementation
- Review regularly, not just at design time