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 agentmods add skills/kazdenc/builder-skills/prdnpx skills add kazdenc/builder-skills --skill prdgit clone --depth 1 https://github.com/kazdenc/builder-skillsWrote 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/kazdenc/builder-skills/prd)<a href="https://agentmods.dev/skills/kazdenc/builder-skills/prd"><img src="https://agentmods.dev/badge/skills/kazdenc/builder-skills/prd.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.00065 | $0.00950 |
| Opus 5 | $0.00032 | $0.00475 |
| Sonnet 5 | $0.00013 | $0.00190 |
| Haiku 4.5 | $0.00006 | $0.00095 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Requirements Document
Write a PRD that answers two questions clearly: what are we building and why does it matter. Everything else is supporting detail.
Step 1: Gather Context
Before writing anything, nail down these three inputs. If the user hasn't provided them, ask.
| Input | Question | Watch out for |
|---|---|---|
| Problem | What pain exists today? Who feels it? | Jumping to solutions before the problem is sharp |
| Audience | Who specifically benefits? What's their situation? | "Everyone" is not an audience |
| Current state | How do people solve this now? What's broken? | Assuming nothing exists today |
If a JTBD analysis, research, or prior conversations exist, pull from them. Don't invent context.
Step 2: Write the PRD
Use this structure. Every section earns its place — skip a section only if it genuinely doesn't apply.
# PRD: [Feature / Product Name]
## Problem Statement
What's broken, missing, or painful. Ground it in real user behavior.
Who has this problem. How often. How bad.
## Goals & Non-Goals
### Goals
- [ ] Measurable outcome this work achieves
- [ ] Another measurable outcome
### Non-Goals
- What this work deliberately does NOT try to solve (and why)
## User Stories / Job Stories
Use job story format when possible:
- When [situation], I want to [motivation], so I can [outcome]
Keep to 3-8 stories. If you have more, the scope is too big.
## Functional Requirements
What the system must do. Number them for traceability.
FR-1: [Requirement]
FR-2: [Requirement]
## Non-Functional Requirements
Performance, security, accessibility, scale, compatibility.
NFR-1: [Requirement]
NFR-2: [Requirement]
## Success Metrics
How we'll know this worked. Be specific:
- Metric + target + timeframe
- e.g., "Reduce average onboarding time from 12 min to under 5 min within 30 days of launch"
## Open Questions
What's unresolved. Who owns answering it. When it needs an answer by.
| # | Question | Owner | Deadline |
|---|----------|-------|----------|
## Out of Scope
What's explicitly excluded from this effort. Prevents scope creep later.
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 · 107 lines · 65 tokens per session scan A 3d419884d0e2
prd is a skill published in the GitHub repository kazdenc/builder-skills (44 stars, last pushed 6mo ago), licensed MIT. It adds 65 tokens to every session and 950 once invoked, about $0.0003 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 skills, from other repositories
commercial-opportunity-review
Review Product, offering, catalog, quote, and sale evidence for commercial opportunities.
demand-triage
Prepare classification, evidence gaps, and score inputs for product demand without crossing the funding boundary.
product-line-performance-review
Roll real Product evidence into a ProductLine review without changing the canonical reporting boundary.
stakeholder-brief
Prepare a concise owner or stakeholder brief with current decisions, evidence, bets, outcomes, roadmap, and provenance.
weekly-intelligence
Review cited market, competitor, customer, and delivery changes for one explicit business-product scope.
investment-preparation
Prepare an evidence-linked product investment packet while preserving the governed funding decision.