Plugin Claude Code
Security-first development skills powered by the F.O.R.G.E. framework. Built by operators, not consultants. Makes Claude security-aware by default with audit, threat modeling, code hardening, attack surface recon, and structured security workflows.
Skill Claude CodeCodex
ALWAYS invoke for security audits and vulnerability assessments of existing code. Use when the user wants a comprehensive security review, asks you to find vulnerabilities, check for OWASP issues, audit a codebase, pentest code, or review a PR for security problems. Triggers on: 'is this secure', 'security review'…
Skill Claude CodeCodex
ALWAYS invoke when reviewing or fixing security in specific code the user has written or is writing. Use for inline secure code review: checking a function for injection, fixing auth logic, hardening an endpoint, reviewing a specific file or PR diff for dangerous patterns. Triggers on: 'review this code', 'is this…
Skill Claude CodeCodex
ALWAYS invoke when the user is starting to build a security-sensitive feature and needs a structured development workflow. Use for: beginning work on auth, payments, PII handling, encryption, or access control systems. Triggers on: 'how should I approach this securely', 'what is the secure way to build this'…
Skill Claude CodeCodex
ALWAYS invoke for attack surface mapping and security posture enumeration. Use when the user wants to inventory what is exposed: endpoints, entry points, trust boundaries, open ports, unauthenticated routes. Triggers on: 'attack surface', 'what is exposed', 'map the endpoints', 'enumerate entry points', 'security…
Skill Claude CodeCodex
ALWAYS invoke when the user is experimenting with unfamiliar technology or wants to try something new safely. Use for safe experimentation guidance: prototyping, trying a new database, adding an unfamiliar library, testing in production-adjacent environments, exploring AI/ML integrations. Triggers on: 'I want to try'…
Skill Claude CodeCodex
ALWAYS invoke for threat modeling and security architecture analysis. Use when the user is designing a system, planning architecture, or wants to understand what could go wrong before writing code. Triggers on: 'threat model', 'what could go wrong', 'how could this be attacked', 'STRIDE', 'security design review'…