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 sachin0034-tech/mini-pm --skill prd-reviewgit clone --depth 1 https://github.com/sachin0034-tech/mini-pmWrote 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/sachin0034-tech/mini-pm/prd-review)<a href="https://agentmods.dev/skills/sachin0034-tech/mini-pm/prd-review"><img src="https://agentmods.dev/badge/skills/sachin0034-tech/mini-pm/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/sachin0034-tech/mini-pm/prd-review"><img src="https://agentmods.dev/badge/skills/sachin0034-tech/mini-pm/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.00094 | $0.01881 |
| Opus 5 | $0.00047 | $0.00941 |
| Sonnet 5 | $0.00019 | $0.00376 |
| Haiku 4.5 | $0.00009 | $0.00188 |
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 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Review Checklist
Covers 2-pagers and 6-pagers. Mark each item ✅ (Yes) · ⚠️ (Partial) · ❌ (No)
| Field | |
|---|---|
| Document Title | |
| Author / Reviewer | |
| Review Date |
0. Opening & Framing
Amazon PRFAQ principle: if the opening doesn't land, leadership stops reading. Check this first.
| # | Check | Status | Notes |
|---|---|---|---|
| 0.1 | Headline / title is a customer benefit statement — not a feature description or internal project name | ||
| 0.2 | First paragraph names the customer, the problem, and the transformation delivered — an unfamiliar exec understands why this matters in under 30 seconds | ||
| 0.3 | Document is free of buzzwords and hype: "revolutionary", "game-changing", "AI-powered", "next-gen", "paradigm shift" | ||
| 0.4 | Narrative is written from the customer's perspective throughout — not the engineer's or the company's |
Notes:
1. Problem & Customer
| # | Check | Status | Notes |
|---|---|---|---|
| 1.1 | Problem is clearly articulated (job-to-be-done) and validated with real customer data or research — not internal assumptions | ||
| 1.2 | Problem statement is a pure pain statement — does NOT hint at or imply a solution | ||
| 1.3 | Negative impact is quantified: time lost, cost, frequency, or scale of affected users | ||
| 1.4 | Customer persona defined with specific roles, industries, and needs; buyer vs. user distinguished if different | ||
| 1.5 | Urgency is clear — explains why now and the cost of inaction | ||
| 1.6 | Existing alternatives called out as insufficient, with a specific reason why they fall short | ||
| 1.7 | MOAT is defined and defensible — data flywheel, workflow lock-in, proprietary training, or switching cost | ||
| 1.8 | Solution is differentiated from ChatGPT, copilots, and commodity AI wrappers | ||
| 1.9 | Validated demand signal present — customer quotes, paid pilots, waitlists, or demonstrated willingness to pay |
Notes:
2. Solution & AI Design
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 · 161 lines · 0 tokens per session scan A 12a2cba08eeb
prd-review is a skill published in the GitHub repository sachin0034-tech/mini-pm (4 stars, last pushed 4mo ago), licensed MIT. It adds 94 tokens to every session and 1,881 once invoked, about $0.0005 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…