security-auditor

Audit code repositories for security vulnerabilities, exposed secrets, and OWASP Top 10 risks.

16|2|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/jshearin01/agent-skills --skill security-auditor-jshearin01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-auditor
Source: https://github.com/jshearin01/agent-skills/tree/main/security-auditor
Command: npx skills add https://github.com/jshearin01/agent-skills --skill security-auditor-jshearin01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Freer from manual security reviews, this skill helps teams identify security risks in code repositories, including exposed secrets, insecure configurations, and OWASP Top 10 vulnerabilities across frontend and backend.

Core Features & Use Cases

  • Secrets detection: scans for hardcoded API keys, tokens, passwords, and credentials across codebases.
  • Vulnerability assessment: evaluates OWASP Top 10 (2025) risks and tracks CWE mappings.
  • Dependency and config review: identifies vulnerable dependencies and insecure deployment settings.
  • Report generation: emits a severity-rated findings report with remediation guidance and a final security posture summary.
  • Use Case: during PR reviews or periodic security assessments, it surfaces actionable issues for developers and security teams.

Quick Start

Provide a code repository and I will perform an end-to-end security audit across frontend, backend, and dependencies to identify secrets, vulnerabilities, and misconfigurations.

Frequently Asked Questions about security-auditor

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

FAQPage Schema
How do I automate code security audits for exposed secrets and vulnerabilities?

Automate code security audits by scanning repositories to detect hardcoded secrets, identify OWASP Top 10 vulnerabilities, and review dependencies. This process evaluates frontend, backend, and configuration files to surface severity-rated findings with actionable remediation guidance.

What is the best way to scan a repository for hardcoded API keys and credentials?

Scanning a repository for hardcoded API keys and credentials involves performing secrets detection across the entire codebase, including tests, docs, and configurations. This identifies exposed tokens and passwords, providing severity-rated findings to help secure sensitive data.

How do I check my codebase for OWASP Top 10 risks during a pull request?

Check for OWASP Top 10 risks during a pull request by running an end-to-end security audit across frontend and backend code. This tracks CWE mappings and evaluates configurations, emitting a report with a final security posture summary for developers.

Does automated vulnerability assessment work across different programming languages and stacks?

Automated vulnerability assessment works across different programming languages and stacks by performing reconnaissance, frontend, and backend audits on repository contents. It evaluates code, dependencies, and deployment settings to identify security risks regardless of the tech stack.

Can I review vulnerable dependencies and insecure deployment settings together?

You can review vulnerable dependencies and insecure deployment settings together during the dependency review phase. This methodology identifies risks in your deployment configurations and dependency trees, incorporating them into a final severity-rated findings report.