What problem does it solve?
It helps you detect and reduce security risks in your Claude Code setup before misconfigurations, prompt injection paths, or unsafe tool access make it into production.
Core Features & Use Cases
- Configuration vulnerability scanning: Audits
.claude/ content for secrets, risky permissions, and injection patterns that commonly lead to compromise.
- Targeted checks across key files: Reviews
CLAUDE.md, .claude/settings.json, mcp.json, hooks/, and agents/*.md for unsafe directives, tool access, and command injection surfaces.
- Severity-based reporting and guidance: Produces graded findings (A–F) so you can prioritize fixes, plus optional auto-fix for safe remediations.
Example use case: After updating your repository’s Claude configuration for a new MCP server and custom hooks, run this scan to catch hardcoded tokens, overly permissive allow lists, and shell/command injection risks before you commit.
Quick Start
Ask your AI assistant to run an AgentShield scan over your project to produce a security report for the .claude/ directory.