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.
/plugin marketplace add assafkip/prd-os/plugin install prd-osWrote 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.
[](https://agentmods.dev/commands/assafkip/prd-os/prd-approve)<a href="https://agentmods.dev/commands/assafkip/prd-os/prd-approve"><img src="https://agentmods.dev/badge/commands/assafkip/prd-os/prd-approve.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once 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 |
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 6d 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.
This is a copy
100% identical to prd-approve — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
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.
- 6d ago First seen · 20 lines · 15 tokens per session scan A 3b124671a7f0
prd-approve is a command published in the GitHub repository assafkip/prd-os (10 stars, last pushed 2mo ago), 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. It is 100% identical to prd-approve, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
screens
Structures product UX screen design — inventory, flow, states, and reusable briefs for external design tools — without generating pixels or UI code.
assumption-test
Surfaces the riskiest business assumption behind the PRD and designs the cheapest test to falsify it before building.
bug-report
Converts a raw bug report from production into a structured, severity-classified item and routes it to the right next step.
hypothesis-check
Confronts each PRD hypothesis with the real measured number, forces an explicit verdict, and triggers a concrete action.
incident
Coordinates the live response to an active production incident — timeline, status, and resolution — then hands off to /renata:retro for the post-mortem.
metrics
Defines or refines product metrics across 4 layers, each with baseline, formula, source, and a kill criteria tripwire.