What problem does it solve? Claude Code configurations (.claude/ directory) can contain hardcoded secrets, overly permissive permissions, prompt injection vectors, and risky MCP server setups that expose projects to security threats. This Skill audits those configuration files automatically so vulnerabilities are caught before they reach production. ## Core Features & Use Cases - Configuration Auditing: Scans CLAUDE.md, settings.json, mcp.json, hooks, and agent definitions for hardcoded secrets, wildcard permissions, command injection, and supply chain risks. - Graded Reports & Auto-Fix: Produces severity-graded findings (A-F scores) in terminal, JSON, Markdown, or HTML formats, and can automatically apply safe fixes like replacing hardcoded secrets with environment variable references. - CI/CD Integration: Runs as a GitHub Action to fail builds on security findings, plus an optional adversarial three-agent deep analysis mode for red team/blue team assessment. - Use Case: Before committing changes to .claude/settings.json, run a scan to verify no Bash(*) wildcards or hardcoded API keys slipped in, then export a JSON report for your CI pipeline. ## Quick Start Ask the agent to scan the current project's .claude directory for security vulnerabilities and report any critical or high severity findings.