Borrowing it
Nothing to install: this file belongs to nurettincoban/ai-prd-workflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nurettincoban/ai-prd-workflow/main/.claude/commands/verify-prd.mdgit clone --depth 1 https://github.com/nurettincoban/ai-prd-workflowWrote 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/nurettincoban/ai-prd-workflow/verify-prd)<a href="https://agentmods.dev/commands/nurettincoban/ai-prd-workflow/verify-prd"><img src="https://agentmods.dev/badge/commands/nurettincoban/ai-prd-workflow/verify-prd/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/nurettincoban/ai-prd-workflow/verify-prd"><img src="https://agentmods.dev/badge/commands/nurettincoban/ai-prd-workflow/verify-prd.svg" alt="Reviewed on agentmods" width="80" 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.00012 | $0.01133 |
| Opus 5 | $0.00006 | $0.00566 |
| Sonnet 5 | $0.00002 | $0.00227 |
| Haiku 4.5 | $0.00001 | $0.00113 |
Grade A, and why
verify-prd 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert product manager tasked with reviewing a Product Requirements Document (PRD). Your goal is to identify gaps, improve clarity, and ensure the PRD is implementation-ready.
Review PRD.md in the current directory and provide actionable feedback. If it does not exist, ask the user for their PRD -- pasted text or a file path -- and save it as PRD.md before proceeding.
Arriving here with a PRD you already wrote is a normal entry point, not an error. Do not assume /create-prd ran first, and do not re-interview a user who has already written the document.
SCOPE THE CHECKLIST TO THE PRODUCT TYPE
First classify the product: web app · mobile app · library/SDK · CLI · service/API · data pipeline · game.
Apply only the sections and checks that fit that type. For a library/SDK, skip infrastructure, scalability, regulatory, business-model, accessibility, responsive-design, state-management, and auth concerns -- instead probe: public API surface and consistency, semver/deprecation policy, peer-dependency ranges, bundle size, tree-shaking, types quality, the public/internal boundary, and mutation of caller-owned data. Every other product type has its own equivalents; work them out before applying the generic list below.
State which product type you classified and which checks you skipped. Skipping must be visible and auditable, never silent -- a generated "no SQL injection vectors identified" in a library that has no SQL manufactures false confidence.
STEP 0: GROUND THE PRD IN REALITY
Before the gap analysis:
- If the PRD names an existing implementation, prototype, or "extracted from" source, READ IT. Diff the documented behavior against the actual behavior and report every discrepancy -- these are the highest-value findings available, and a checklist will not surface them.
- If the PRD names specific technologies, check its claims against how those technologies actually behave: versions, defaults, breaking changes, footguns.
- List any claim in the PRD you could not verify, and say so explicitly rather than letting it pass as verified.
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.
- 9d ago First seen · 99 lines · 12 tokens per session scan A fbbf1fb817fa
verify-prd is a command published in the GitHub repository nurettincoban/ai-prd-workflow (285 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 1,133 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.
Other commands, from other repositories
enhance-prompt
Command "enhance-prompt" from VoDaiLocz/Enhance-Prompt, covering enhance prompt workflow, 1. intake and scoring (enhance-prompt/skill.md), 5. ambiguity check and 8. iteration (enhance-prompt/references/iteration-mode.md).
camp-init
Create a new camp with the standard directory structure. A camp was previously called a campaign; camp init is the same command either way.
fest-commit
Commit changes with festival traceability metadata.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
fest-list
List all festivals with their status and completion percentage.
lfe-session
You are acting as a senior framework architect helping improve the Library-First Engineering (LFE) framework. This is a META session — you are working ON the framework, not WITH it. Do NOT run the LFE pipeline (/lfe-boot, /lfe-architect, etc.) — those are for product repos that use LFE as a template.