security-audit

Audit code changes for leaked secrets, SQL injection, and sensitive data exposure.

3|Updated Mar 26, 2026

Search Tags:#security #secrets #static-analysis #rate-limiting #pii #code-audit

Ready to run

npx skills add https://github.com/The13thNode/VibeCorp_PromptCEO --skill security-audit-the13thnode

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/The13thNode/VibeCorp_PromptCEO/tree/main/skills/public/security-audit
Command: npx skills add https://github.com/The13thNode/VibeCorp_PromptCEO --skill security-audit-the13thnode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill catches common security regressions introduced by code changes so teams can detect leaked secrets, unsafe queries, sensitive data exposure, and reintroduced prohibited functionality before shipping.

Core Features & Use Cases

Leaked secrets detection: Grep-based checks for hardcoded API keys, tokens, and passwords in source files not protected by environment variables.
Injection and PII checks: Identify unparameterised SQL, console leaks of sensitive fields, missing masking in UI, and missing rate limiting on auth routes.
Use Case: Run at the end of a development session or on a pull request to produce a PASS/FAIL report with file locations and recommended fixes.

Quick Start

Run a full security audit and return PASS or FAIL for each check with file paths and remediation guidance.

Frequently Asked Questions about security-audit

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

FAQPage Schema

How do I check my code changes for leaked secrets and sensitive data exposure?▼

To check code changes for leaked secrets and sensitive data exposure, run an automated security audit that performs grep-based detection for hardcoded API keys, tokens, passwords, and verifies missing data masking in your UI.

What is the best way to automate pull request security checks for SQL injection and rate limiting?▼

The best way to automate pull request security checks is to run an automated security audit that identifies unparameterised SQL queries and verifies missing rate limiting on authentication routes before shipping code changes.

How does static analysis detect unparameterised SQL queries and prohibited functionality patterns?▼

Static analysis detects unparameterised SQL queries and prohibited functionality patterns by scanning source files during a code audit, checking for unsafe queries, and verifying type safety to prevent security regressions.

Can I run a security audit on both frontend and backend repositories for an end-of-session review?▼

Yes, you can run a security audit on both frontend and backend repositories for an end-of-session review, producing a PASS or FAIL report that includes file locations and recommended remediation steps for detected vulnerabilities.

Does automated code auditing work without external dependencies or environment variables?▼

Automated code auditing works without external dependencies, relying on static analysis and grep-based checks to find hardcoded credentials in source files not protected by environment variables and detect unsafe code patterns.

Why does my security audit report FAIL on console leaks of sensitive fields and missing data masking?▼

Your security audit reports FAIL on console leaks and missing data masking because the static analysis checks identify sensitive data exposure in your frontend UI and flag unmasked sensitive fields for immediate remediation.