Security Code Review

Detects high-severity vulnerabilities through data-flow tracking and auth bypass pattern analysis.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill security-code-review-kaminocorp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Security Code Review
Source: https://github.com/kaminocorp/hermes-alpha-hunter/tree/main/hunter/skills/security/code-review-security
Command: npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill security-code-review-kaminocorp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual security code review often misses deep vulnerabilities like IDOR, race conditions, and auth bypasses because they require tracing user input across many layers of code. This Skill provides a systematic methodology for finding exploitable, high-severity vulnerabilities with clear proof-of-concept evidence. ## Core Features & Use Cases - Deep Data-Flow Tracking: Trace user-controlled input from entry points through transformations to dangerous sinks like SQL queries, shell commands, and file operations. - Auth Bypass Pattern Detection: Identify incomplete authorization checks, JWT validation flaws, OAuth misconfigurations, IDOR, and TOCTOU race conditions. - Severity Calibration: Assign Critical/High/Medium/Low severity only when a reproducible exploit path exists, reducing false positives. - Use Case: Reviewing a Django REST API before launch, trace request parameters into ORM queries, find an endpoint missing an ownership check, and document a working IDOR exploit with a step-by-step PoC. ## Quick Start Review this codebase for security vulnerabilities, tracing user input to dangerous sinks and reporting only findings with reproducible exploit paths.

Frequently Asked Questions about Security Code Review

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

FAQPage Schema
How do I find auth bypass vulnerabilities in code review?▼

Trace every endpoint's authorization logic and check whether it verifies resource ownership, not just authentication. Look for IDOR patterns where user-controlled IDs reach database queries without ownership checks, JWT validation flaws like algorithm confusion, and race conditions between check and use.

How to trace data flow for SQL injection detection?▼

Identify entry points like request parameters, headers, and file uploads, then follow the data through variable assignments, function calls, and string concatenations until it reaches a SQL query. Flag any path where user input reaches raw queries without parameterization.

What severity should I assign to a reflected XSS finding?▼

Reflected XSS without persistence is typically Medium severity, while stored XSS in an admin panel qualifies as High. Only assign Critical or High when you can document a clear step-by-step exploit path with a working proof of concept.

Does this security review approach work for Node.js and PHP code?▼

Yes, the methodology includes technology-specific patterns for Python/Django/Flask, Node.js/Express, PHP, and Java/Spring. Each section lists dangerous functions and idioms per stack, such as eval() in Node.js or unserialize() in PHP.

When should a finding not be reported in a security review?▼

Do not report findings that require the user to already be compromised, physical device access, or social engineering as the primary vector. Theoretical issues without evidence of occurrence or a reproducible three-step PoC should also be excluded.