security-auditor

Scan codebases for security vulnerabilities and secret leaks.

7|3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/brainbrewlabs/brainbrew-devkit --skill security-auditor-brainbrewlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-auditor
Source: https://github.com/brainbrewlabs/brainbrew-devkit/tree/main/plugin/config/templates/devops/skills/security-auditor
Command: npx skills add https://github.com/brainbrewlabs/brainbrew-devkit --skill security-auditor-brainbrewlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects security vulnerabilities, secret exposures, and risky dependency issues in source code so teams can fix problems before they reach production.

Core Features & Use Cases

  • Automated checks for OWASP Top 10 patterns such as SQL injection, XSS, and broken access control.
  • Secrets detection for hardcoded credentials and verification that environment files are properly ignored.
  • Dependency audits using platform-specific tools (npm audit, pip-audit, govulncheck) for pre-deploy or pull request scans.
  • Use cases include reviewing changes touching authentication, API, or database layers, scanning updated dependency manifests, and running pre-deployment security gates.

Quick Start

Run a security audit on the changed files and produce a severity-classified Security Audit Report.

Frequently Asked Questions about security-auditor

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

FAQPage Schema
How do I scan code for security vulnerabilities before deployment?

To scan code for security vulnerabilities before deployment, apply an automated audit to changed files touching authentication or database layers to detect OWASP Top 10 risks and produce a severity-classified report.

Can I detect hardcoded secrets and credentials in my source code?

Yes, you can detect hardcoded secrets and credentials in source code by running secrets detection scans that search for exposed keys and verify your environment files are properly ignored.

What is the best way to audit dependencies for known vulnerabilities in a pull request?

The best way to audit dependencies for known vulnerabilities in a pull request is running platform-specific tools like npm audit, pip-audit, or govulncheck against updated dependency manifests to identify risky packages.

Does this security audit check for OWASP Top 10 patterns like SQL injection and XSS?

Yes, this security audit checks for OWASP Top 10 patterns like SQL injection and XSS by performing pattern-based source searches across your codebase to identify common vulnerability signatures.

When should I run a code audit for security vulnerabilities?

You should run a code audit for security vulnerabilities when reviewing changes to API layers, scanning updated dependency manifests, or executing pre-deployment security gates to catch issues before production.