What problem does it solve? Claude Code configurations like CLAUDE.md, settings.json, and MCP server definitions can contain hardcoded secrets, overly permissive permissions, and prompt injection vectors that are easy to miss during manual review. This Skill audits your .claude/ directory and reports graded findings before they become production risks. ## Core Features & Use Cases - Configuration Auditing: Scans CLAUDE.md, settings.json, mcp.json, hooks, and agent definitions for secrets, dangerous permissions, and injection patterns. - Auto-Fix and CI Integration: Applies safe automatic fixes and outputs JSON, Markdown, or HTML reports suitable for GitHub Actions pipelines. - Deep Adversarial Analysis: Runs an optional three-agent red team, blue team, and auditor pipeline for deeper threat assessment. - Use Case: Before committing a new .claude/ setup to a shared repository, run a scan to catch a hardcoded API key in mcp.json and an unrestricted Bash(*) allow rule, then auto-fix both. ## Quick Start Ask the assistant to run a security scan on the current project's .claude directory and report any critical or high severity findings.