prd-approve

prd-approve is a command for Claude Code from assafkip/kipi-system. It costs 15 tokens per session (159 once invoked), scanned A, original, MIT.

A command that marks an active PRD as approved. A PRD, or product requirements document, describes what should be built and why.

In plain words
What is it for?
Use it after every finding has been given a decision, then continue by splitting the PRD into separate issue specifications.
Why use it?
It stops approval while review findings are still unresolved or the findings record is invalid.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the prd-os plugin — 2 skills, 9 commands shipped together

Good fit Use it after every finding has been given a decision, then continue by splitting the PRD into separate issue specifications.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add assafkip/kipi-system
Claude Code
/plugin install prd-os

Made for: Claude Code.

Or install prd-os, the plugin that ships this one along with the rest of its 2 skills, 9 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for prd-approve

README.md
[![agentmods](https://agentmods.dev/badge/commands/assafkip/kipi-system/prd-approve.svg)](https://agentmods.dev/commands/assafkip/kipi-system/prd-approve)
Your own site
<a href="https://agentmods.dev/commands/assafkip/kipi-system/prd-approve"><img src="https://agentmods.dev/badge/commands/assafkip/kipi-system/prd-approve.svg" alt="Measured on agentmods" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 159 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.00159
Opus 5 $0.00008 $0.00079
Sonnet 5 $0.00003 $0.00032
Haiku 4.5 $0.00002 $0.00016

Measured 8d ago against content hash 3b124671a7f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

prd-approve scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/prd-os/commands/prd-approve.md · 20 lines

What it actually says

Approve the active PRD. The runner's findings gate blocks approval when any finding is still pending or the findings JSONL contains an invalid line.

Do not bypass by editing the findings file. If the gate blocks, run /prd-triage to set dispositions, then retry this command.

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/prd_runner.py" advance approved

On success, tell the author the next step is /prd-split to materialize the PRD's issue manifest into one issue spec per entry.

On block, surface stderr verbatim. The runner names the offending finding ids.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 20 lines · 15 tokens per session scan A 3b124671a7f0

Subscribe to this mod's changes

prd-approve is a command published in the GitHub repository assafkip/kipi-system (110 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 159 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.