
from claude-skills8,729
Provides concrete guidance and code examples to implement authentication, authorization, input validation, and other defenses against OWASP Top 10 vulnerabiliti
Secure Code Guardian gives an engineering-focused playbook for designing, implementing, and validating web application security controls. It walks through threat modeling, defensive design, and concrete implementation patterns (password hashing, parameterized SQL, JWT validation, input validation with Zod, security headers, rate limiting) and provides code examples and validation checkpoints so engineers can ship secure features with repeatable tests.
Invoke this skill when building or reviewing authentication/authorization flows, handling user input, configuring tokens or sessions, or hardening endpoints against OWASP Top 10 classes (XSS, SQLi, broken auth, etc.). It fits pull-request reviews, security design sessions, and implementation checklists before release.
Broadly applicable to code-focused agents that can produce and review code (Claude Code, Copilot-style assistants, Codex/GitHub Copilot).
Secure Code Guardian is a reference-style skill providing OWASP Top 10 secure coding guidance with concrete TypeScript/Node.js code examples for password hashing, parameterized queries, input validation, JWT handling, and endpoint security. Well-structured SKILL.md with clear MUST DO/MUST NOT DO constraints and validation checkpoints. No bundled scripts — purely a reference/knowledge skill. Security posture is strong: explicitly advocates against hardcoding secrets, recommends env vars, uses parameterized queries, and promotes constant-time comparison. Minor deduction for referencing process.env.JWT_SECRET! without noting fallback validation, and the full-flow example uses 'your-app' as issuer which could be copied literally.
Solid security-focused skill with good code examples and clear constraints. No malicious patterns detected. Advocates for security best practices throughout. Architecture follows skill spec with frontmatter, references section, and code examples. Could improve with more specific trigger conditions and a tighter description.