What problem does it solve?
It prevents capability leaks, injection paths, and supply-chain risks when code changes touch sandbox boundaries, IPC/plugin surfaces, untrusted strings, file paths, process spawning, or network access.
Core Features & Use Cases
- Rigid security review for specific change triggers: Runs when relevant areas are touched (hook/IPC/plugin manifests, payloads with model/tool/external output, new dependencies, filesystem/process/network access, plugin exposed surfaces).
- Three threat models in one note: Evaluates sandbox escape/capability leakage, prompt injection/untrusted content flows, and supply chain from package.json changes.
- Structured PR output contract: Produces a concise “## Security review” block with explicit “N/A: <reason>” coverage and mandatory reasoning for every section.
Quick Start
Use this skill by reviewing a PR diff that adds a new dependency or modifies IPC/plugin loading, then paste the generated structured “## Security review” checklist into your pull request description.