security-review

Audit codebases for OWASP Top 10 vulnerabilities and hardcoded secrets.

1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/MartinNevlaha/stratus-v2 --skill security-review-martinnevlaha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/MartinNevlaha/stratus-v2/tree/main/cmd/stratus/skills/security-review
Command: npx skills add https://github.com/MartinNevlaha/stratus-v2 --skill security-review-martinnevlaha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of identifying common security vulnerabilities in code, ensuring a higher level of security and compliance.

Core Features & Use Cases

  • Vulnerability Auditing: Scans code for hardcoded secrets, authentication flaws, input validation issues, path traversal, SQL injection, and dependency risks.
  • OWASP Top 10 Coverage: Addresses key security categories defined by the OWASP Top 10.
  • Use Case: Before deploying new code, run a security review to catch critical issues like exposed API keys or insecure endpoints, preventing potential breaches.

Quick Start

Run a security review on the current codebase, focusing on hardcoded secrets and input validation.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I scan my codebase for hardcoded secrets and SQL injection vulnerabilities?

Scanning for hardcoded secrets and SQL injection involves running a comprehensive security audit that detects authentication flaws, input validation weaknesses, and dependency risks while checking against OWASP Top 10 categories.

What is a code security audit against the OWASP Top 10?

A code security audit against the OWASP Top 10 is an automated review process that identifies vulnerabilities like path traversal, broken authentication, and sensitive data exposure to ensure compliance and prevent potential breaches.

Can I check for path traversal and sensitive data exposure in version control configurations?

Yes, you can check for path traversal and sensitive data exposure by auditing version control configurations to detect hardcoded secrets and insecure endpoints before deploying new code.

When should I run a security audit on my code to catch critical issues?

You should run a security audit before deploying new code to catch critical issues like exposed API keys or insecure endpoints, ensuring a higher level of security and compliance.

Does this security review check for dependency risks and authentication flaws?

Yes, the security review checks for dependency risks and authentication flaws as part of a comprehensive audit that detects hardcoded secrets, input validation issues, and path traversal vulnerabilities.