Back to catalog / Security
Security threat modeling: enumerate trust boundaries and abuse paths
Map entry points, identities, assets, and attacker capabilities to prioritized threats.
Skills
Trigger only for an explicit threat-model/AppSec request. Scope to the named repo/path; identify entry points, assets, trust boundaries, attacker capabilities, and runtime/CI separation. Build evidence-backed abuse cases and map mitigations to concrete components. Mark unresolved facts as assumptions, explain risk and prerequisites, and follow the source template’s quality check. Write `<repo-or-dir>-threat-model.md`. A report is not authorization to exploit vulnerabilities or scan external targets.
Permissions
Prerequisites
- Create an evidence-grounded threat model for a repository or path when explicitly requested.
Permissions
- Reads architecture/code and writes a threat-model Markdown file that may contain sensitive details.
Limitations
Trigger only on explicit request; label evidence/assumptions and stay within the named scope.
Pinned upstream source
- Repository
- openai/skills
- File path
- skills/.curated/security-threat-model/SKILL.md
- Pinned commit
49f948faa9258a0c61caceaf225e179651397431- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: Apache-2.0
Compatible tools
repository inspection · prompt template · threat model references
Main topic
Make Agent behavior safer and easier to verify