What problem does it solve?
Manually reviewing Claude Code configuration files for security issues is error-prone and time-consuming, leaving projects vulnerable to hardcoded secrets, prompt injection, and misconfigured permissions that could lead to data breaches or unauthorized access.
Core Features & Use Cases
- Multi-File Security Audit: Scans CLAUDE.md, settings.json, MCP server configs, hooks, and agent definitions for common security flaws.
- Actionable Remediation Guidance: Categorizes findings by severity (A-F grade) and provides clear steps to fix critical, high, and medium risk issues.
- Use Case: Before pushing .claude configuration changes to a shared team repository, run this scan to catch hardcoded API keys or dangerous hook command injection patterns that could expose sensitive project data.
Quick Start
Use the security-scan skill to audit your current project's .claude directory for security vulnerabilities and receive a prioritized remediation report.