agent-security-reviewer

Reviews code for OWASP Top 10 vulnerabilities, hardcoded secrets, and insecure patterns.

5|15|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/clfigueiredo/hermes-infra-skills --skill agent-security-reviewer-clfigueiredo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-security-reviewer
Source: https://github.com/clfigueiredo/hermes-infra-skills/tree/main/.hermes/skills/curso-hermes/agent-security-reviewer
Command: npx skills add https://github.com/clfigueiredo/hermes-infra-skills --skill agent-security-reviewer-clfigueiredo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It catches security vulnerabilities in code before they reach production, flagging hardcoded secrets, injection risks, broken authentication, and unsafe handling of user input. ## Core Features & Use Cases - OWASP Top 10 Review: Systematically checks injection, broken auth, sensitive data exposure, XSS, misconfiguration, and insecure deserialization. - Secrets and Pattern Detection: Flags hardcoded API keys, string-concatenated SQL, shell commands with user input, and missing rate limiting with severity ratings and fixes. - Use Case: After writing a new API endpoint that accepts user input and queries a database, run this review to get actionable findings listing each problem, its impact, and the concrete remediation. ## Quick Start Ask the agent to review your recent code changes for security vulnerabilities and list each finding with its severity and recommended fix.

Frequently Asked Questions about agent-security-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review code for security vulnerabilities before deployment?▼

Run a structured review covering the OWASP Top 10: injection, broken authentication, sensitive data exposure, XSS, and misconfiguration. This skill scans for hardcoded secrets, unsafe patterns like string-concatenated SQL, and missing auth checks, returning findings with severity and fixes.

What code patterns indicate critical security vulnerabilities?▼

Critical patterns include hardcoded secrets, shell commands built from user input, string-concatenated SQL queries, plaintext password comparison, routes without authentication checks, and balance checks without database locking. Each should be fixed before release.

Does this security review work with Node.js and npm projects?▼

Yes, it includes commands like npm audit and eslint-plugin-security for dependency and static analysis. The review patterns also apply generally to web applications handling authentication, APIs, and user input regardless of framework.

When should I run a security review on my code?▼

Run it after writing code that handles user input, authentication, API endpoints, database queries, file uploads, or payments. Also run it immediately after dependency CVEs, production incidents, or before major releases.

Why does the review flag things that are not real vulnerabilities?▼

Common false positives include placeholder values in .env.example files, clearly marked test credentials, intentionally public API keys, and MD5 or SHA256 used for checksums rather than passwords. Always verify context before treating a finding as a real issue.