Security Audit Kit
Find the vulnerabilities before someone else does. A defensive review stack in the order a security engineer would run it: model the threats, review the code against OWASP, run static analysis and dependency, secret and container scans, test the running app within an agreed scope, and write findings up with severities a team can act on.
What's inside
Best for: Engineers and security reviewers with authorization to test the system. Start with threat-modeling and secure-code-review. Each skill loads when a request matches its description, or call one directly with its $name.
- Threat Modeling STRIDE threats tied to real data flows
- Secure Code Review Security review of a diff, done right
- OWASP Top 10 Review Find real OWASP bugs at file:line
- Semgrep SAST A ruleset you trust, gated on new bugs
- Dependency Scanning Triage CVEs to fixes, not alert counts
- Secret Scanning Rotate first, then purge history
- Container Scanning Fix the base, not one CVE at a time
- Pentest Methodology Scope, exploit, document, report
- API Security Testing Prove BOLA with two tokens
- Security Audit Report Findings an engineer can fix and an exec can read