security-scan

Audit Claude Code configurations for security vulnerabilities using AgentShield.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits Claude Code configurations to identify security vulnerabilities, misconfigurations, and risky patterns across project files using AgentShield.

Core Features & Use Cases

  • Scan CLAUDE.md for insecure prompts and auto-run instructions.
  • Validate settings.json and MCP configs for overly permissive permissions.
  • Inspect hooks and agent definitions for potential data exfiltration or prompt injection.

Quick Start

Run the AgentShield scanner against your repository's Claude Code configuration to detect and remediate security issues.

Frequently Asked Questions about security-scan

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

FAQPage Schema
How do I audit Claude Code configurations for security vulnerabilities?

Scanning MCP configurations for overly permissive permissions identifies risky access controls in your settings.json and mcp.json files. AgentShield validates these configs to prevent unauthorized tool access and potential data exfiltration.

How do I check CLAUDE.md for insecure prompts and auto-run instructions?

Checking CLAUDE.md for insecure prompts involves scanning the file for risky auto-run instructions and prompt injection vulnerabilities. AgentShield inspects agent definitions and configuration files to detect and remediate these security issues.

Does AgentShield work with MCP configs and hooks directories?

Yes, AgentShield works with MCP configs and hooks directories by inspecting settings.json, mcp.json, hooks/, and agents/*.md files. It validates these configurations for potential data exfiltration and prompt injection risks.

What is the best way to scan repository configurations for prompt injection?

The best way to scan repository configurations for prompt injection is running a dedicated security audit tool like AgentShield. It inspects agent definitions and hook scripts to identify potential injection vectors and data exfiltration risks.

Can I export security audit findings from Claude Code configs in JSON or Markdown?

Yes, you can export security audit findings from Claude Code configs in JSON, Markdown, HTML, and terminal formats. AgentShield generates these reports after scanning your repository for configuration vulnerabilities.