Scan your Claude Code configuration (.claude/ directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions. Use when auditing a .claude/ directory — CLAUDE.md, settings.json, MCP servers,

Security Scan Skill Audit your Claude Code configuration for security issues using [AgentShield](https://github.com/affaan m/agentshield). When to Activate Setting up a new Claude Code project After modifying .claude/settings.json , CLAUDE.md , or MCP configs Before committing configuration changes When onboarding to a new repository with existing Claude Code configs Periodic security hygiene checks What It Scans File Checks CLAUDE.md Hardcoded secrets, auto run instructions, prompt injection patterns settings.json Overly permissive allow lists, missing deny lists, dangerous bypass flags mcp.json Risky MCP servers, hardcoded env secrets, npx supply chain risks hooks/ Command injection via interpolation, data exfiltration, silent error suppression agents/ .md Unrestricted tool access, prompt injection surface, missing model specs Prerequisites AgentShield must be installed. Check and install if needed: Usage Basic Scan Run against the current project's .claude/ directory: Output Formats Auto Fix Apply safe fixes automatically (only fixes marked as auto fixable): This will: Replace hardcoded secrets with environment variable references Tighten wildcard permissions to scoped alternatives Never modify manual only suggestions Opus 4.6 Deep Analysis Run the adversarial three agent pipeline for deeper analysis: This runs: 1. Attacker (Red Team) — finds attack vectors 2. Defender (Blue Team) — recommends hardening 3. Auditor (Final Verdict) — synthesizes both perspectives Initialize Secure Config Scaffold a new secure .claude/ configuration from scratch: Creates: settings.json with scoped permissions and deny list CLAUDE.md with security best practices mcp.json placeholder GitHub Action Add to your CI pipeline: Severity Levels Grade Score Meaning A 90 100 Secure configuration B 75 89 Minor issues C 60 74 Needs attention D 40 59 Significant risks F 0 39 Critical vulnerabilities Interpreting Results Critical Findings (fix immediately) Hardcoded API keys or tokens in config files Bash( ) in the allow list (unrestricted shell access) Command injection in hooks via ${file} interpolation Shell running MCP servers High Findings (fix before production) Auto run instructions in CLAUDE.md (prompt injection vector) Missing deny lists in permissions Agents with unnecessary Bash access Medium Findings (recommended) Silent error suppression in hooks ( 2 /dev/null , true ) Missing PreToolUse security hooks npx y auto install in MCP server configs Info Findings (awareness) Missing descriptions on MCP servers Prohibitive instructions correctly flagged as good practice Links GitHub : [github.com/affaan m/agentshield](https://github.com/affaan m/agentshield) npm : [npmjs.com/package/ecc agentshield](https://www.npmjs.com/package/ecc agentshield)

security-scan