What problem does it solve? Web applications that accept user input, manage sessions, or integrate external services are exposed to injection, XSS, broken access control, SSRF, and supply-chain attacks. This Skill provides a structured threat-modeling process and concrete prevention patterns so security is built into every feature rather than bolted on later. ## Core Features & Use Cases - Threat Modeling with STRIDE: Map trust boundaries, name assets, and run a quick STRIDE analysis before writing security controls, addressing OWASP A04 Insecure Design. - OWASP Prevention Patterns: Ready-to-use code patterns for parameterized queries, bcrypt password hashing, secure session cookies, CSP headers, CORS restriction, schema validation with Zod, and file upload safety. - SSRF and LLM Security: Defend server-side URL fetches with host allowlists and private-IP rejection, and treat LLM output as untrusted input per the OWASP LLM Top 10. - Use Case: When adding a webhook endpoint that fetches user-supplied URLs, apply the SSRF allowlist pattern to block requests to cloud metadata IPs like 169.254.169.254 before shipping. ## Quick Start Review my new API endpoint for security vulnerabilities and apply the appropriate hardening patterns from the security checklist.