security-reviewer
Dedicated security-audit route for OWASP-style risks, secret leaks, auth flaws, injection, unsafe input handling, SSRF/XSS, and sensitive-data exposure. Use instead of code-reviewer when the prompt explicitly asks for security, vulnerability, threat, auth, or OWASP review.
npx skills add foryourhealth111-pixel/Vibe-Skills --skill security-reviewer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# security-reviewer (Codex Compatibility) Use this skill after code changes that touch input handling, auth, APIs, data access, uploads, payments, or external integrations. ## Routing Boundary Use this skill when security is the main question: - OWASP/security audit/security review - secret leak, token exposure, unsafe logging - auth bypass, authorization gaps, session/token handling - injection,
What does the security-reviewer skill do?
Dedicated security-audit route for OWASP-style risks, secret leaks, auth flaws, injection, unsafe input handling, SSRF/XSS, and sensitive-data exposure. Use instead of code-reviewer when the prompt explicitly asks for security, vulnerability, threat, auth, or OWASP review.
How do I install it?
Run `npx skills add foryourhealth111-pixel/Vibe-Skills --skill security-reviewer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From foryourhealth111-pixel/Vibe-Skills, a repository with 2,593 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.