security-auditor

Name: security-auditor
Availability: InStock
Author: miptah21

Scan codebases for security vulnerabilities and produce PASS/WARN/FAIL reports.

2|Updated Apr 8, 2026

Search Tags:#security audit #secret detection #vulnerability scanning #secure deployment #code injection #dependency risk #auth bypass

Ready to run

npx skills add https://github.com/miptah21/skills --skill security-auditor-miptah21

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-auditor
Source: https://github.com/miptah21/skills/tree/main/.agents/skills/security-auditor
Command: npx skills add https://github.com/miptah21/skills --skill security-auditor-miptah21

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires os, sys, re, and includes scripts (resource) components.

What problem does it solve?

It helps you discover security vulnerabilities in a codebase before release so you can reduce the risk of compromise, exposure, and abuse.

Core Features & Use Cases

Security scanning across risk classes: Flags command execution, code execution, XSS/auth bypass patterns, secret leakage, and supply-chain concerns.
Clear PASS / WARN / FAIL reporting: Produces a categorized verdict with remediation-oriented guidance so teams know what to fix first.
Use Case: Auditing a recently updated repository after adding new dependencies or handling auth, payments, or PII to ensure common high-impact issues are addressed.

Quick Start

Run the security audit against your repository to generate a categorized verdict and actionable findings.

Frequently Asked Questions about security-auditor

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

FAQPage Schema

How do I scan a codebase for security vulnerabilities before deployment?▼

Scanning a codebase for security vulnerabilities involves checking source and configuration files for risky patterns like command injection, XSS, and auth bypass. This skill generates a categorized PASS/WARN/FAIL report with remediation guidance to fix issues before release.

What's the best way to audit dependencies for supply chain risk signals?▼

Auditing dependencies for supply chain risk involves reviewing newly added packages for unsafe execution or vulnerable patterns. This skill evaluates repositories after dependency changes to detect supply-chain concerns and outputs a categorized PASS/WARN/FAIL report with actionable findings.

Can I detect command injection and XSS vulnerabilities in source files?▼

Detecting command injection and XSS vulnerabilities in source files requires pattern matching against risky code execution and cross-site scripting behaviors. This skill scans target codebases to flag these security flaws and generates a verdict report with remediation-oriented guidance.

Does this security audit tool check for auth bypass patterns in configuration files?▼

Security audit tools that check for auth bypass patterns scan both source and configuration files for risky authentication logic. This skill flags auth bypass vulnerabilities during pre-deployment audits and post-incident re-audits, producing a clear PASS/WARN/FAIL report.

When should I run a post-incident security re-audit on my repository?▼

A post-incident security re-audit should be run after a compromise or exposure event to ensure common high-impact issues are addressed. This skill re-scans source and configuration files for command execution, secret exposure, and injection patterns to verify remediation.

What does a PASS WARN FAIL security report include for code remediation?▼

A PASS/WARN/FAIL security report includes categorized verdicts and remediation-oriented guidance so teams know what to fix first. This skill generates this report format after scanning for vulnerabilities, secret leakage, and supply-chain concerns across the target codebase.