security-scan

Scan Claude Code configuration files for security vulnerabilities and injection risks.

Updated May 4, 2026
One-click install
npx skills add https://github.com/gganbukim1/myskills --skill security-scan-gganbukim1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-scan
Source: https://github.com/gganbukim1/myskills/tree/main/security-scan
Command: npx skills add https://github.com/gganbukim1/myskills --skill security-scan-gganbukim1

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about security-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan my Claude Code configuration for security vulnerabilities?

To scan Claude Code configuration for vulnerabilities, run an AgentShield scan over your project to audit `.claude/` directories, which checks for secrets, risky permissions, and injection patterns.

What types of prompt injection risks are detected in MCP server definitions?

Prompt injection risks in MCP server definitions are detected by reviewing `mcp.json` for unsafe directives, risky tool access, and command injection surfaces that could compromise your setup.

Can I automatically fix misconfigurations found in CLAUDE.md and settings.json?

Yes, you can automatically fix misconfigurations in `CLAUDE.md` and `.claude/settings.json` using the optional auto-fix feature for safe remediations after the scan produces severity-graded findings.

Does the security scan check hook scripts for command injection surfaces?

Yes, the security scan checks hook scripts under `hooks/` for command injection surfaces, alongside reviewing agent configuration files and MCP server definitions for unsafe tool access.

How are security findings reported and prioritized for Claude Code setups?

Security findings for Claude Code setups are reported as severity-graded scores from A to F, allowing you to prioritize fixes for hardcoded tokens, overly permissive allow lists, and shell injection risks.

When should I run a configuration vulnerability scan on my agents directory?

You should run a configuration vulnerability scan on your `agents/*.md` directory after updating repository configurations for new MCP servers and custom hooks, ensuring no unsafe directives reach production.