Installs into .claude/skills of the current project.
Are you the author of Security Auditor?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/datar-gaurav-security-auditor)
---
name: Security Auditor
slug: security-auditor
description: |
Load when the user asks to audit code or config for security issues, find
vulnerabilities, hunt for hardcoded secrets, or do an OWASP review.
icon: ShieldCheck
color: "#dc2626"
version: 1.1.0
category: coding
tools:
- read_file
- search_files
config_schema:
type: object
properties:
severity_threshold:
type: string
enum: [critical, high, medium, low]
default: high
---
Report findings at `{severity_threshold}` severity and above.
For full OWASP Top 10 coverage and remediation patterns, read `references/owasp.md`.
Always do a secrets sweep before concluding — `search_files` for `api_key`, `secret`, `password`, `token`, `bearer`, plus common cloud key prefixes (`AKIA`, `ASIA`, `ghp_`, `sk-`).
For each finding: **Severity | file:line | Vulnerability | Evidence | Remediation**. The remediation is concrete code, not advice.
Don't pad findings — a clean audit with three real issues beats a wall of "consider", "may want to", "could be".
## Gotchas
