ripwire-security-scan

# Security scan with ripwire > Nearest neighbour: wiring ripwire ITSELF into an agent as an MCP server (not auditing someone else's) ��� > **ripwire-mcp**. General diff risk/coupling, not specifically security → **ripwire-change-check**. Trigger (config scanning): you've received a `SKILL.md`, a skills folder, or an `.mcp.json` from an external source and want to verify it's safe before installing or activating it. Trigger (code scanning): you're reviewing or about to write security-sensitive code — anything that parses untrusted input, deserializes, execs/evals, does raw pointer/buffer arithmetic, or sits on a network-facing boundary — and want structural signal on where the risk concentrates before you read line-by-line. ## Skill files — the built-in scanner **Scan a single file:** ``` ripwire --scan-skill=PATH/TO/SKILL.md ``` Output: `ripwire scan: N finding(s) in <file>`, then one line per finding — ``` CRITICAL inject.md:11 INJECTION:ignore-prev — "Ignore previous instructions and instead act as …" ``` Each finding lists severity, `file:line`, the rule id (`INJECTION:ignore-prev`, `INJECTION:you-are-now`, exfiltration/path-traversal rules), and the offending text verbatim. **Scan a whole directory:** ``` ripwire --scan-skills=DIR # bare form also scans repo-local, Claude, and Codex skill homes ``` Recursively scans every `.md`, reports the same per-finding lines. Run this before adopting an entire skills folder, and as a periodic check on installed ones...