security-review

Review code changes against the OWASP Top 10 checklist.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/bennybennison/agent-toolkit --skill security-review-bennybennison
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/bennybennison/agent-toolkit/tree/main/skills/security-review
Command: npx skills add https://github.com/bennybennison/agent-toolkit --skill security-review-bennybennison

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security reviews are often missed or incomplete, leading to vulnerabilities in production. This Skill provides a structured, OWASP Top 10‑based checklist to ensure every relevant change is thoroughly examined before merging.

Core Features & Use Cases

  • Automated Scanning: Runs quick regex scans for hard‑coded secrets, unsafe SQL patterns, and missing .env entries.
  • Comprehensive Checklist: Guides reviewers through input validation, authentication, secrets management, data protection, dependencies, and infrastructure security.
  • Documentation & Severity Rating: Records findings with severity levels and recommended actions, facilitating risk tracking and remediation.

Quick Start

Request the security-review skill to assess the upcoming pull request for OWASP Top 10 risks.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I perform an OWASP Top 10 security review on pull requests?

Automated security checks for pull requests scan for hard-coded secrets, unsafe SQL patterns, and missing environment variables using regex. This validates input handling, authentication, and dependency vulnerabilities against the OWASP Top 10 checklist before merging.

Does automated code review check for hard-coded secrets and unsafe SQL patterns?

Automated code review checks for hard-coded secrets and unsafe SQL patterns by running quick regex scans. It verifies missing .env entries, input validation, and dependency vulnerabilities to ensure code changes meet OWASP Top 10 security standards before merging.

Can I use this security checklist for APIs, file operations, and third-party integrations?

You can use this security checklist for APIs, file operations, and third-party integrations. It applies structured OWASP Top 10 reviews to any pull requests modifying authentication, input handling, database queries, or environment variables to ensure comprehensive protection.

What is the best way to document security findings and severity levels during a code review?

The best way to document security findings during a code review is to record them with severity levels and recommended actions. This facilitates risk tracking and remediation by guiding reviewers through vulnerabilities found in dependencies, data protection, and infrastructure.

When do I need to run an OWASP Top 10 security checklist before merging code?

You need to run an OWASP Top 10 security checklist before merging code when pull requests modify APIs, authentication, input handling, file operations, database queries, third-party integrations, or environment variables to prevent production vulnerabilities.