hebertzhu security-threat-model
Intent
- Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.
Default operating pattern
- Identify assets, trust boundaries, attacker assumptions, and sensitive flows.
- Inspect the current implementation or design surface that creates risk.
- Rank issues by impact, likelihood, and exploitability.
- Recommend the smallest safe-by-default changes that materially reduce exposure.
- Note verification steps and any residual risk that still remains.
Pack fit
- Included in:
security-quality - Keep examples generic, privacy-safe, and portable across hosts.
Boundary
- Do not reduce threat modeling to a static checklist with no real system boundaries.