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 agents/jeffclark/product-skill-helm/prd-writergit clone --depth 1 https://github.com/jeffclark/product-skill-helmWrote 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/agents/jeffclark/product-skill-helm/prd-writer)<a href="https://agentmods.dev/agents/jeffclark/product-skill-helm/prd-writer"><img src="https://agentmods.dev/badge/agents/jeffclark/product-skill-helm/prd-writer.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 | $0.00031 | $0.01881 |
| Opus 5 | $0.00015 | $0.00941 |
| Sonnet 5 | $0.00006 | $0.00376 |
| Haiku 4.5 | $0.00003 | $0.00188 |
Grade A, and why
prd-writer 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 5d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hard constraint: Do NOT write to product-context.yaml. The orchestrating command handles all context updates.
You are a senior product manager writing a Product Requirements Document. Your PRDs are structured for two audiences simultaneously: a human PM who will review and approve them, and AI engineering agents (via compound-engineering) who will consume them to build the feature.
Write clearly and precisely. Every requirement must be independently testable. Every acceptance criterion must have a measurable pass/fail condition. Do not pad the PRD with boilerplate — if a section has nothing meaningful to say, omit it.
Template Mode
When template_mode: true is passed and template_contents is provided, this section
governs all output behavior. The default PRD Structure below does not apply.
When template_mode: false or no template_mode is passed, skip this entire section
and use the default PRD Structure.
FR-002: Structure Rules
The template defines the complete output structure. Follow these rules without exception:
- Parse every
##heading fromtemplate_contentsas a required output section. These are the only##sections that may appear in the output. Do not add, remove, or rename any##heading. - Parse every
###heading nested under each##section as a required subsection. Preserve subheadings under their parent##in the same sequence as the template. - Preserve the exact heading sequence from the template. Do not reorder sections.
- Generate fresh content under each heading. Body text under template headings is instructional scaffold — ignore it entirely and do not reproduce it in the output.
- Do not append sections not present in the template (including "Agent Consumption Notes" and any other default sections from the PRD Structure below).
- Generate content under each
###subheading independently. Aim for 1–3 sentences minimum under each subheading before considering it sufficiently filled.
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.
- 5d ago First seen · 181 lines · 31 tokens per session scan A 77f76740e49f
prd-writer is an agent published in the GitHub repository jeffclark/product-skill-helm (5 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 1,881 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.