What problem does it solve? Security-sensitive code changes often ship without a clear threat model, leaving gaps in input validation, authorization, secret handling, and dependency safety that only surface after an incident. ## Core Features & Use Cases - Threat Modeling: Records assets, actors, trust boundaries, abuse cases, and required invariants before any security-sensitive change. - Baseline Security Controls: Applies explicit checks for input validation, parameterized queries, output encoding, server-side authorization, secret hygiene, and safe file/URL handling. - Approval Gates and Review Workflow: Pauses for explicit approval before changing authentication, authorization, sensitive-data, or integration behavior, then verifies with tests, static analysis, and diff review. - Use Case: When adding a file upload endpoint, use this Skill to trace the input path, constrain file size and destination, enforce server-side authorization, and verify no secrets or stack traces leak in error responses. ## Quick Start Review this authentication change for security issues and list the trust boundaries, controls checked, and residual risks before I approve it.
