Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add adamfaik/claude-code-pm-starter --skill prd-reviewgit clone --depth 1 https://github.com/adamfaik/claude-code-pm-starterWrote 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/skills/adamfaik/claude-code-pm-starter/prd-review)<a href="https://agentmods.dev/skills/adamfaik/claude-code-pm-starter/prd-review"><img src="https://agentmods.dev/badge/skills/adamfaik/claude-code-pm-starter/prd-review/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/skills/adamfaik/claude-code-pm-starter/prd-review"><img src="https://agentmods.dev/badge/skills/adamfaik/claude-code-pm-starter/prd-review.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.00052 | $0.00390 |
| Opus 5.5 | $0.00021 | $0.00156 |
| Sonnet 5.5 | $0.00010 | $0.00078 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
prd-review 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 1mo 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.
What it actually says
PRD review
Be the demanding colleague who reads the draft before the real audience does. Findings, not a rewrite.
Steps
- Load the bar. Read
context/preferences.md(writing preferences and corrections log),context/users.md(who this is ultimately for), and the project'sbrief.mdif the document belongs to a project. - Read the document end to end before flagging anything.
- Review against four lenses, in order of importance:
- The problem. Is it stated with evidence, or assumed? Would someone who disagrees be convinced there's a problem at all?
- The decision. What is this document asking the reader to decide or accept? If you can't find it, that's the first finding.
- The evidence. Every claim needs a source, a number, or a named observation. Flag each claim that has none.
- The edges. What's out of scope, what could go wrong, what's the cost of being wrong? Silent edges get flagged.
- Check it against the user's own rules. Anything in the corrections log that this draft violates gets flagged with the rule quoted.
Output
Prioritized findings: must-fix first, then should-fix, then nits. Each finding quotes the passage, says what's wrong in one line, and proposes the concrete fix. Cap at ten findings; if there are more, the top ten are the review. End with the one-line verdict you'd give the user across a desk: ready to share, or not yet, and why.
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.
- 1mo ago First seen · 24 lines · 52 tokens per session scan A bb9e543f582e
prd-review is a skill published in the GitHub repository adamfaik/claude-code-pm-starter (13 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 390 once invoked, about $0.0002 per session on Opus 5.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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…