security-audit
SolidUse when performing security vulnerability assessment (OWASP, secrets, dependencies, IaC, LLM, API, MCP/agentic) or when "thinking like a hacker" to find exploits.
Install
Quality Score: 80/100
Skill Content
Details
- Author
- MatrixFounder
- Repository
- MatrixFounder/Agentic-development
- Created
- 7 months ago
- Last Updated
- today
- Language
- Python
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
security-audit
Use when reviewing code for common vulnerabilities (SQL injection, XSS, leaked secrets, unsafe eval) and proposing concrete fixes.
security-audit
OWASP Top 10 + STRIDE threat model pass on the current codebase, or on the current branch diff. Emits a findings report with severity, confidence, and exploit scenario. Use alongside Claude Code's built-in /security-review for spot checks, and whenever the diff touches auth, credentials, tool policy, shell execution, or data persistence. Adapted from Garry Tan's gstack /cso (garrytan/gstack); role framing stripped.
security-audit
Audits code for common vulnerabilities: injection, secrets, auth, and dependency CVEs — with confidence-gated, evidence-backed findings mapped to CWE/OWASP. Use when reviewing security, before a release, after adding auth/payments/sensitive-data handling, or when the user says 'security review', 'security audit', 'check for vulnerabilities', 'is this secure'. Do not use for auditing what a public client discloses about a private backend — use public-client-leak-audit for that.