Provides expert knowledge for implementing and reviewing application security following OWASP Top 10 (2021), with stack-specific patterns for Spring Boot, Django, Next.js, and Astro.
Provides expert knowledge for implementing and reviewing application security following OWASP Top 10 (2021), with stack-specific patterns for Spring Boot, Django, Next.js, and Astro.
Project-wide security audit (OWASP Top 10, auth, access control, headers, secrets, dependencies). Run before go-live and after major changes. Mandatory gate before /deploy prod.
The single security skill — diff/PR audit method with a high-confidence bar (BOLA/IDOR, mass assignment, DTO validation, injection, secrets, rate limiting), STRIDE threat modeling before large features, backend auth hardening (guards, Passport, RBAC, CORS/CSRF, OWASP ASVS), and mobile hardening (MASVS: token storage, deep links, WebView, build config). Load the SKILL.md for routing, then read ONLY the references/ file matching the job.
Audits and hardens code against the OWASP Top 10 — input validation, authn/authz, secrets management, cryptography, and dependency scanning with CWE mapping. Trigger with "security review", "is this endpoint secure", "scan our dependencies", or "where do we store this secret".
Apply security best practices to protect applications, data, and users from vulnerabilities. TRIGGER this skill automatically when the user mentions: SQL injection, XSS, CSRF, authentication bypass, input validation, sanitizing user input, environment variables or secrets management, HTTPS, rate limiting, permission checks, authorization, security audit, vulnerability, or any phrase like "is this secure?", "how do I protect", "prevent attacks", or "secure this endpoint". Also trigger when reviewing code that handles user-supplied data, passwords, tokens, API keys, or database queries.
Defensive security review of a repo, diff, PR, dependency set or config, using tiered subagents. Deterministic scanners run first, cheap models map the attack surface, a stronger model hunts by category, and a different model family tries to disprove each finding before it is reported. Use when the user types /security, or asks for a "security review", "security audit", "is this safe to merge", "check for vulns/secrets", or "threat model this". Defensive only, for code and systems the user owns or is authorized to assess.
Reviews and implements web security boundaries, authorization, output encoding, session protection, and secret handling. Use for security-sensitive changes or a requested security review.
Secure web and desktop application development. Use when writing authentication, authorization, API endpoints, form handling, database queries, file uploads, Electron apps, Tauri apps, IPC handlers, cryptography, secrets management, security headers, input validation, or when reviewing code for vulnerabilities. Covers OWASP Top 10, XSS, CSRF, SQL injection, SSRF, command injection, path traversal, and desktop app security. Also usable as a support sub-skill: other skills can invoke it by name mid-build to check code or a design for vulnerabilities before finalizing.
Multi-session defensive security coach: prompt injection, data leaks, agent safety, and incident response, taught with inert examples. Use only when asked to start or continue this course.
Finds and fixes vulnerabilities in code the user owns across web, API, and LLM surfaces, and owns confidentiality for authorized remote credential handoffs. Use for a security review, "is this safe to ship," "check for vulnerabilities," "보안 점검," secrets hygiene, dependency risk, PR security regressions, or "hand a secret to a remote agent." Not for building LLM-agent systems, Orca session operation (use official `orca-cli`), or general hook and gate configuration; this skill never attacks.
Practical application security — injection, authentication, authorization, secrets, and input validation. Use when writing any code that handles user input, auth, files, money, or personal data; when reviewing for vulnerabilities; or when storing credentials.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.