security-checklist

Automate security code reviews using OWASP patterns and secrets detection.

9|5|Updated Aug 8, 2025
One-click install
npx skills add https://github.com/AnExiledDev/CodeForge --skill security-checklist-anexileddev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-checklist
Source: https://github.com/AnExiledDev/CodeForge/tree/main/.devcontainer/plugins/devs-marketplace/plugins/code-directive/skills/security-checklist
Command: npx skills add https://github.com/AnExiledDev/CodeForge --skill security-checklist-anexileddev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Identify and address code security vulnerabilities early by guiding a comprehensive review using OWASP Top 10 patterns and secrets detection.

Core Features & Use Cases

  • Provides structured guidance for security reviews across codebases, including OWASP patterns and secret-detection references.
  • Supports rapid assessments for code audits, vulnerability scanning, and dependency checks across multiple languages.
  • Helps teams standardize security reviews and improve discovery of hard-coded credentials, insecure configurations, and vulnerable dependencies.

Quick Start

Audit a codebase for security issues using OWASP patterns.

Frequently Asked Questions about security-checklist

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

FAQPage Schema
How do I automate a security code audit using OWASP patterns?

Automate a security code audit by applying OWASP Top 10 patterns to scan for vulnerabilities and detect hard-coded secrets across multiple languages. This structured review identifies insecure configurations and vulnerable dependencies early in development.

What is the best way to detect hard-coded secrets and credentials in my codebase?

Detect hard-coded secrets by scanning your codebase against dedicated secrets-patterns references. This automated review checks for exposed credentials and insecure configurations to standardize vulnerability discovery across your project.

Can I perform a vulnerability scan across multiple programming languages?

Yes, you can perform vulnerability scanning and dependency checks across multiple programming languages. The review applies standardized security patterns to identify risks regardless of the specific tech stack used.

How do I check for insecure configurations and vulnerable dependencies during a code review?

Check for insecure configurations and vulnerable dependencies by running an automated security review guided by OWASP patterns. This process standardizes discovery to highlight risks during standard code audits.

Does this security review approach require any specific file formats or setup?

The security review requires a YAML frontmatter containing the name and description fields to initialize. It then loads vulnerability and secrets detection rules from specific markdown reference files to execute the audit.