security-scan

name	security-scan
description	Scan your tool configuration for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks instruction files, settings, MCP servers, hooks, and agent definitions.

Security Scan Skill

Audit your tool configuration for security issues using AgentShield.

When to Activate

• Setting up a new tool-enabled project
• After modifying tool config, instruction files, or MCP configs
• Before committing configuration changes
• When onboarding to a new repository with existing MDT tool configs
• Periodic security hygiene checks

What It Scans

File	Checks
Instruction file (AGENTS.md, CLAUDE.md, equivalent)	Hardcoded secrets, auto-run instructions, prompt injection patterns
Tool settings/config	Overly permissive allow lists, missing deny lists, dangerous bypass flags
MCP config	Risky MCP servers, hardcoded env secrets, npx supply chain risks
Hooks	Command injection via interpolation, data exfiltration, silent error suppression
Agent definitions	Unrestricted tool access, prompt injection surface, missing model specs

Prerequisites

AgentShield must be installed. Check and install if needed:

# Check if installed
npx MDT-agentshield --version

# Install globally (recommended)
npm install -g MDT-agentshield

# Or run directly via npx (no install needed)
npx MDT-agentshield scan .

Usage

Basic Scan

Run against the current tool or project config directory:

# Scan current project
npx MDT-agentshield scan

# Scan a specific path
npx MDT-agentshield scan --path /path/to/tool-config

# Scan with minimum severity filter
npx MDT-agentshield scan --min-severity medium

Output Formats

# Terminal output (default) — colored report with grade
npx MDT-agentshield scan

# JSON — for CI/CD integration
npx MDT-agentshield scan --format json

# Markdown — for documentation
npx MDT-agentshield scan --format markdown

# HTML — self-contained dark-theme report
npx MDT-agentshield scan --format html > security-report.html

Auto-Fix

Apply safe fixes automatically (only fixes marked as auto-fixable):

npx MDT-agentshield scan --fix

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:

# Requires ANTHROPIC_API_KEY
export ANTHROPIC_API_KEY=your-key
npx MDT-agentshield scan --opus --stream

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:

npx MDT-agentshield init

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:

- uses: affaan-m/agentshield@v1
  with:
    path: '.'
    min-severity: 'medium'
    fail-on-findings: true

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 instruction files (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
• npm: npmjs.com/package/MDT-agentshield