audit-security

Scans Claude Code plugins for leaked secrets, path traversal, and shell injection risks.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/JaviMontano/mao-plugin-qa --skill audit-security-javimontano
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-security
Source: https://github.com/JaviMontano/mao-plugin-qa/tree/main/skills/audit-security
Command: npx skills add https://github.com/JaviMontano/mao-plugin-qa --skill audit-security-javimontano

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Claude Code plugins can accidentally ship with leaked API keys, hardcoded paths, injectable hook commands, or sensitive credential files. This Skill performs a six-category static security audit on a plugin directory and produces a severity-classified report with specific remediation for every finding. ## Core Features & Use Cases - Secret Detection: Scans all files for API keys (sk-, AKIA, ghp_*), private keys, passwords, and .env files, classifying matches as CRITICAL. - Hook & Script Analysis: Inspects hook commands for eval usage, unquoted variables, backtick substitution, and external URLs that could exfiltrate data. - Path & File Safety: Flags hardcoded absolute paths, path traversal patterns, and sensitive files like .pem, .key, or credentials.json. - Use Case: Before publishing a plugin to a marketplace, run the audit to catch a leaked OpenAI key in hooks.json and an unvalidated curl download in a setup script, then fix them using the provided remediation advice. ## Quick Start Run a security audit on the plugin at ./my-plugin and report all findings with severity levels and remediation steps.

Frequently Asked Questions about audit-security

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

FAQPage Schema
How do I check a Claude Code plugin for leaked API keys?▼

Run a security audit that scans all plugin files for credential patterns like sk-*, AKIA*, ghp_*, private key headers, and .env files containing KEY= or SECRET= entries. Each match is reported as CRITICAL with the exact file path and line number.

How to detect shell injection risks in plugin hook commands?▼

Inspect hook definitions for eval usage, backtick substitution, unquoted variable expansion, and commands piped to sh or bash. Static analysis of the command strings flags these injection vectors as CRITICAL without executing them.

Does the security audit modify or delete files it flags?▼

No, the audit is strictly read-only. It never modifies, deletes, or quarantines files; it only reports findings with severity, location, and recommended remediation for you to apply manually.

Why does secret scanning produce false positives in documentation?▼

Generic patterns like password= often appear in examples and comments. The audit mitigates this with context checking, classifying template placeholders like ${API_KEY} as INFO rather than CRITICAL, though edge cases can still occur.

What are the limitations of pattern-based secret detection?▼

Pattern-based scanning cannot detect secrets that are obfuscated, encrypted, or split across multiple variables. Suspicious base64 blobs over 40 characters are flagged as INFO for manual review instead.