security-review

Identify security gaps in codebases and configurations with remediation checklists.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/EvilBit-Labs/opnConfigGenerator --skill security-review-evilbit-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/EvilBit-Labs/opnConfigGenerator/tree/main/.claude/skills/security-review
Command: npx skills add https://github.com/EvilBit-Labs/opnConfigGenerator --skill security-review-evilbit-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Security Review Skill helps teams identify and remediate security gaps in codebases, configurations, and deployment processes by providing structured guidance and best-practice patterns.

Core Features & Use Cases

  • Security checklists: step-by-step guidance for secrets management, input validation, authentication, authorization, data exposure, and secure coding patterns.
  • Practical patterns: examples and references for safe handling of credentials, tokens, and user input.
  • Not applicable contexts: notes when upstream security topics do not apply to offline CLI tools like opnConfigGenerator.

Quick Start

Run a security audit across your repository using the included checklists and patterns to identify hardcoded secrets and insecure practices.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I perform a security review on my codebase to find hardcoded secrets and insecure practices?

A security review identifies gaps in your codebase by applying a structured checklist to secrets management, input validation, and authentication. It provides non-destructive, actionable remediation steps and references to canonical security practices for offline CLI projects.

What areas of authentication and authorization are checked during a code security audit?

Authentication and authorization checks assess how user credentials, tokens, and access controls are implemented. The audit applies structured patterns to verify safe handling of credentials and ensures data exposure risks are identified and remediated.

Can I use this security audit checklist for offline CLI projects and local configurations?

Yes, the security audit is explicitly designed for offline CLI projects. It includes notes on when upstream security topics do not apply to local configurations, ensuring the checklist remains relevant to your deployment process.

What is the best way to check for input validation and data exposure risks in my repository?

The best way to check for data exposure is to run a security audit using included checklists. These provide step-by-step guidance and practical patterns for validating user input and preventing sensitive data leakage.

Does the security review automatically fix secrets handling and insecure coding patterns?

No, the security review is non-destructive and does not automatically modify code. It identifies insecure coding patterns in secrets handling and provides practical examples and references for you to implement the remediation manually.