codex-security-review

Analyze code for security vulnerabilities using OWASP Top 10 and CWE patterns.

69|23|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/lploc94/codex_skill --skill codex-security-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-security-review
Source: https://github.com/lploc94/codex_skill/tree/main/skill-packs/codex-review/skills/codex-security-review
Command: npx skills add https://github.com/lploc94/codex_skill --skill codex-security-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of identifying security vulnerabilities in code, helping developers proactively address risks before they are exploited.

Core Features & Use Cases

  • Vulnerability Detection: Scans code for common security flaws based on OWASP Top 10 and CWE patterns.
  • Automated Reporting: Generates detailed reports with findings, severity, and suggested fixes.
  • Use Case: Before merging a pull request, run this Skill to get an immediate security assessment, ensuring that no critical vulnerabilities like SQL injection or hardcoded secrets are introduced.

Quick Start

Use the codex-security-review skill to perform a high-effort security review of your current branch.

Frequently Asked Questions about codex-security-review

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

FAQPage Schema
How do I automate security code review before a pull request merge?

Automate security code review by running static analysis on your working-tree or branch to identify OWASP Top 10 vulnerabilities and hardcoded secrets. This Skill generates detailed reports with severity levels and suggested fixes, ensuring critical flaws like SQL injection are caught before merging.

Can static analysis detect OWASP Top 10 vulnerabilities like injection flaws and broken access control?

Static analysis detects OWASP Top 10 vulnerabilities by scanning code patterns for injection flaws, broken access control, secrets exposure, and misconfigurations. It uses CWE patterns to identify these security risks proactively, providing automated assessments of potential exploitation points.

What is the best way to scan a full codebase for hardcoded secrets and misconfigurations?

The best way to scan a full codebase for hardcoded secrets and misconfigurations is using automated static analysis with configurable review scopes. You can target the working-tree, specific branch, or entire codebase to identify security vulnerabilities based on CWE patterns.

How do I run a security vulnerability scan on a specific git branch?

Run a security vulnerability scan on a specific git branch by configuring the review scope to target that branch. The static analysis uses configurable effort levels to evaluate code for injection flaws, broken access control, and secrets exposure, integrating with the OpenAI Codex CLI for deterministic execution.

Does this static analysis tool require any external dependencies to run?

This static analysis tool requires no external dependencies to run. It operates independently using scripts and references components to conduct automated security reviews and generate detailed vulnerability reports based on OWASP Top 10 and CWE patterns.

What severity levels and fix suggestions are included in automated security reports?

Automated security reports include findings categorized by severity levels and provide suggested fixes for detected vulnerabilities. The reports cover security flaws identified through OWASP Top 10 and CWE pattern matching, offering detailed insights for addressing injection flaws, broken access control, and secrets exposure.