security-scan

Scan Claude Code configurations for security vulnerabilities and misconfigurations.

Updated May 24, 2023
One-click install
npx skills add https://github.com/Kimjiman/basic-arch --skill security-scan-kimjiman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-scan
Source: https://github.com/Kimjiman/basic-arch/tree/main/.claude/skills/security-scan
Command: npx skills add https://github.com/Kimjiman/basic-arch --skill security-scan-kimjiman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and helps mitigate security vulnerabilities, misconfigurations, and potential injection risks within your Claude Code project's configuration files and agent definitions.

Core Features & Use Cases

  • Vulnerability Scanning: Audits .claude/ directory for security flaws.
  • Configuration Analysis: Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.
  • Use Case: Before deploying a new Claude Code project or after making significant configuration changes, run this skill to ensure your setup is secure and adheres to best practices, preventing potential breaches or unintended agent behaviors.

Quick Start

Run the security scan against the current project's .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 Claude Code configurations for security vulnerabilities?

To scan Claude Code configurations for security vulnerabilities, run a security scan against the `.claude` directory to audit files like `CLAUDE.md`, `settings.json`, and agent definitions using AgentShield. This identifies hardcoded secrets, injection risks, and overly permissive allow lists.

What security risks exist in Claude Code MCP servers and hooks?

Security risks in Claude Code MCP servers and hooks include command injection, hardcoded secrets, overly permissive allow lists, and unrestricted tool access. Analyzing these configuration files detects misconfigurations that could lead to potential breaches or unintended agent behaviors.

When should I run a security audit on my Claude Code project?

You should run a security audit on your Claude Code project before deploying a new setup or after making significant configuration changes. Scanning the `.claude` directory ensures your configurations adhere to security best practices and prevents unintended agent behaviors.

Does AgentShield detect hardcoded secrets in Claude Code settings.json?

Yes, AgentShield detects hardcoded secrets in `settings.json` by analyzing the file for security flaws. The scan audits the entire `.claude` directory to identify sensitive data exposure, misconfigurations, and unrestricted tool access within your agent definitions.

What is the best way to secure a Claude Code agent configuration?

The best way to secure a Claude Code agent configuration is to run a vulnerability scan that analyzes `CLAUDE.md`, MCP servers, and hooks. This process identifies command injection risks and overly permissive allow lists to ensure your setup adheres to best practices.