p:security-review

Automate security audits of code and plan artifacts with structured findings.

1|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/pontscho/prompt-heaven --skill p-security-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: p:security-review
Source: https://github.com/pontscho/prompt-heaven/tree/main/ClaudeCode/skills/p%3Asecurity-review
Command: npx skills add https://github.com/pontscho/prompt-heaven --skill p-security-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Multi-mode security audits address the need to assess both code and plan artifacts for security risks, ensuring thorough coverage across development workflows.

Core Features & Use Cases

  • CODE mode: 3-phase security assessment with isolated sub-agent contexts for triage, findings, verification, and assembly.
  • PLAN mode: inline plan-level audit that quickly evaluates threat surfaces in markdown plans with no sub-agents.
  • Auto-infer mode with explicit overrides and structured outputs (verdicts, findings, and remediation guidance) across code and plan targets.

Quick Start

Run /p:security-review <target> to initiate a mode-appropriate security audit.

Frequently Asked Questions about p:security-review

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

FAQPage Schema
How do I automate a security audit for my code and markdown plans?

To automate a security audit, you can run a command that initiates a mode-appropriate assessment. The system auto-infers whether to evaluate code or plan artifacts and outputs structured findings, verdicts, and remediation guidance.

Can I use a single tool to assess both code and plan-level security threats?

Yes, you can use a multi-mode security audit tool to assess both code and plan artifacts. It supports a 3-phase code assessment pipeline and a single-pass inline plan audit to evaluate threat surfaces.

How does the code security review process work?

The code security review process works through a 3-phase pipeline using isolated sub-agent contexts for triage, finding, verification, and assembly. This comprehensive approach ensures thorough coverage of potential vulnerabilities.

What is the best way to audit a markdown plan for security risks?

The best way to audit a markdown plan for security risks is using a single-pass plan-level audit. This inline evaluation quickly assesses threat surfaces in plan artifacts without requiring complex sub-agents.

Does the security audit tool output structured data for downstream automation?

Yes, the security audit tool enforces a frontmatter contract and outputs structured findings, verdicts, and remediation guidance. This structured format is designed specifically for consumption by downstream automation tooling.