Security Detection

Security Detection Utility

Triggers

When to Use

Use this skill when:

• Committing changes that may touch infrastructure or security files
• Pre-commit validation for security-sensitive paths
• Determining if a security agent review is needed
• CI pipeline security gate checks

Use the security agent directly instead when:

• You already know security review is needed
• Performing threat modeling or vulnerability assessment
• Reviewing authentication or authorization code in depth

Available Scripts

Usage

# Analyze staged files
python detect_infrastructure.py --git-staged

# Analyze specific files
python detect_infrastructure.py .github/workflows/ci.yml src/auth/login.cs

Output

When security-critical files are detected:

=== Security Review Detection ===

CRITICAL: Security agent review REQUIRED

Matching files:
  [CRITICAL] .github/workflows/deploy.yml
  [HIGH] src/Controllers/AuthController.cs

Run security agent before implementation:
  Task(subagent_type="security", prompt="Review infrastructure changes")

When no matches:

No infrastructure/security files detected.

Risk Levels

Detected Patterns

Critical (Review Required)

• CI/CD workflows (.github/workflows/*)
• Git hooks (.githooks/*, .husky/*)
• Authentication code (**/Auth/**, **/Security/**)
• Environment files (*.env*)
• Credentials and keys (*.pem, *.key, *secret*)

High (Review Recommended)

• Build scripts (build/**/*.ps1, scripts/**/*.sh)
• Container configs (Dockerfile*, docker-compose*)
• API controllers (**/Controllers/**)
• App configuration (appsettings*.json)
• Infrastructure as Code (*.tf, *.tfvars, *.bicep)

Integration

Pre-commit Hook

Add to .githooks/pre-commit:

# Security detection (non-blocking warning)
python3 .claude/skills/security-detection/detect_infrastructure.py --git-staged

CI Integration

- name: Check security-critical files
  run: python .claude/skills/security-detection/detect_infrastructure.py --git-staged

Exit Codes

The scripts are designed to be non-blocking warnings. They always exit 0 to avoid blocking commits or CI. The warning is informational only.

Customization

Edit the pattern lists in either script to add or modify detection patterns:

• CRITICAL_PATTERNS / $CriticalPatterns - Review required
• HIGH_PATTERNS / $HighPatterns - Review recommended

Process

1. Gather the list of changed files (staged or explicit)
2. Run pattern matching against critical and high-risk file patterns
3. Report findings with risk level classification
4. Route to security agent if CRITICAL matches found

Anti-Patterns

Verification

After running security detection:

• Script exited with code 0 (non-blocking)
• All CRITICAL matches reviewed
• Security agent routed for CRITICAL findings
• HIGH matches evaluated for review need
• Output captured in session log if security-relevant

Related Documents

• Infrastructure File Patterns
• Security Agent Capabilities
• Orchestrator Routing Algorithm

Converted and distributed by TomeVault — claim your Tome and manage your conversions.