What problem does it solve? Claude Code configurations (CLAUDE.md, settings.json, MCP servers, hooks, agent definitions) can contain hardcoded secrets, overly permissive permissions, prompt injection vectors, and command injection risks that are easy to miss during manual review. ## Core Features & Use Cases - Configuration Auditing: Scans CLAUDE.md, settings.json, mcp.json, hooks, and agent definitions for secrets, dangerous permissions, and injection patterns, producing a graded report (A-F). - Auto-Fix and CI Integration: Applies safe automatic fixes for issues like hardcoded secrets and wildcard permissions, and outputs JSON, Markdown, or HTML reports suitable for CI/CD pipelines via a GitHub Action. - Deep Adversarial Analysis: Runs an optional three-agent red team/blue team/auditor pipeline for deeper threat analysis. - Use Case: Before committing changes to .claude/settings.json, run a scan to catch a Bash(*) wildcard permission or a hardcoded API key before it reaches production. ## Quick Start Scan my current project's Claude Code configuration for security issues and show me any critical or high severity findings.