code-security-audit

Scan application code for OWASP Top 10 vulnerabilities and hardcoded secrets.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/AdeptMind/pr-emojis-in-slack --skill code-security-audit-adeptmind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-security-audit
Source: https://github.com/AdeptMind/pr-emojis-in-slack/tree/main/.claude/skills/security/code-security-audit
Command: npx skills add https://github.com/AdeptMind/pr-emojis-in-slack --skill code-security-audit-adeptmind

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill proactively identifies and flags security vulnerabilities within your application code, helping to prevent breaches and protect sensitive data.

Core Features & Use Cases

  • OWASP Top 10 Scanning: Detects common web application security risks like injection flaws, broken access control, and insecure cryptography.
  • Secret Detection: Flags hardcoded API keys, passwords, and other sensitive credentials.
  • Use Case: Before deploying a new feature, run a code-security-audit on the relevant modules to ensure no critical vulnerabilities are introduced, such as SQL injection or exposed secrets.

Quick Start

Run a code security audit on the 'src/api' directory.

Frequently Asked Questions about code-security-audit

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

FAQPage Schema
How do I scan my application code for OWASP Top 10 vulnerabilities?

To scan application code for OWASP Top 10 vulnerabilities, run a security audit targeting your project root or specific directories. The audit identifies languages and frameworks to apply specific checks for injection flaws, broken access control, and insecure cryptography.

How do I find hardcoded secrets and API keys in my source code?

Finding hardcoded secrets and API keys in source code is handled by the audit's secret detection feature. It flags hardcoded passwords and sensitive credentials, providing severity levels and remediation advice to secure your application.

What is the best way to check for SQL injection and cross-site scripting (XSS) before deployment?

The best way to check for SQL injection and cross-site scripting (XSS) before deployment is to run a targeted code security audit on relevant modules. This proactively identifies and flags critical vulnerabilities with specific remediation advice.

Can I run a security audit on a specific directory like 'src/api' instead of the whole project?

Yes, you can run a security audit on a specific directory like 'src/api' instead of the whole project. The audit analyzes code based on provided arguments, defaulting to the project root if no specific path is supplied.

How does a code security audit handle different programming languages and frameworks?

A code security audit handles different programming languages and frameworks by first identifying them within the target codebase. It then applies specific checks tailored to the detected technologies to accurately flag vulnerabilities and insecure cryptography.

What severity levels are reported when detecting cross-site request forgery (CSRF) and other security flaws?

When detecting cross-site request forgery (CSRF) and other security flaws, the audit reports critical, high, medium, and low severity levels. Each finding includes actionable remediation advice to help resolve the identified vulnerabilities.