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.
git clone --depth 1 https://github.com/unixcrh/phuryn-pm-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/commands/unixcrh/phuryn-pm-skills/write-prd)<a href="https://agentmods.dev/commands/unixcrh/phuryn-pm-skills/write-prd"><img src="https://agentmods.dev/badge/commands/unixcrh/phuryn-pm-skills/write-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/unixcrh/phuryn-pm-skills/write-prd"><img src="https://agentmods.dev/badge/commands/unixcrh/phuryn-pm-skills/write-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.00013 | $0.00933 |
| Opus 5 | $0.00006 | $0.00466 |
| Sonnet 5 | $0.00003 | $0.00187 |
| Haiku 4.5 | $0.00001 | $0.00093 |
Grade A, and why
write-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 10d 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.
This is a copy
100% identical to write-prd — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/write-prd -- Product Requirements Document
Create a structured PRD that aligns stakeholders and guides development. Accepts anything from a vague idea to a detailed brief.
Invocation
/write-prd SSO support for enterprise customers
/write-prd Users are dropping off during onboarding — we need to fix step 3
/write-prd [upload a brief, research doc, or strategy deck]
Workflow
Step 1: Understand the Feature
Accept the input in any form:
- A feature name ("SSO support")
- A problem statement ("Enterprise customers keep asking for centralized auth")
- A user request ("Users want to export their data as CSV")
- A vague idea ("We should do something about onboarding drop-off")
- An uploaded document (brief, research, Slack thread, email)
Step 2: Gather Context
Ask conversationally — most important questions first, fill gaps as you go:
- User problem: What problem does this solve? Who experiences it? How painful is it?
- Target users: Which user segment(s)? How many? What's their current workaround?
- Success metrics: How will we know this worked? What moves if we nail it?
- Constraints: Technical constraints, timeline, regulatory, dependencies on other teams?
- Prior art: Has this been attempted before? Existing solutions in the market?
- Scope preference: Full solution or phased approach?
If the user provides a document with context, extract what's available and only ask about gaps.
Step 3: Generate the PRD
Apply the create-prd skill to produce an 8-section document:
## Product Requirements Document: [Feature Name]
**Author**: [user]
**Date**: [today]
**Status**: Draft
**Stakeholders**: [if known]
### 1. Executive Summary
[2-3 sentences: what, for whom, why now]
### 2. Background & Context
[Problem space, prior research, market context, what prompted this]
### 3. Objectives & Success Metrics
**Goals** (what success looks like):
1. [Specific, measurable goal]
2. [...]
**Non-Goals** (explicitly out of scope):
1. [What we're not doing, and why]
2. [...]
**Success Metrics**:
| Metric | Current | Target | Measurement |
|--------|---------|--------|-------------|
### 4. Target Users & Segments
[Who this serves, user profiles, segment sizing]
### 5. User Stories & Requirements
**P0 — Must Have**:
| # | User Story | Acceptance Criteria |
|---|-----------|-------------------|
**P1 — Should Have**:
| # | User Story | Acceptance Criteria |
|---|-----------|-------------------|
**P2 — Nice to Have / Future**:
| # | User Story | Acceptance Criteria |
|---|-----------|-------------------|
### 6. Solution Overview
[High-level approach, key design decisions, technical approach if known]
### 7. Open Questions
| Question | Owner | Deadline |
|----------|-------|----------|
### 8. Timeline & Phasing
[Milestones, dependencies, phasing if applicable]
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.
- 10d ago First seen · 119 lines · 13 tokens per session scan A 7c7a1646905e
write-prd is a command published in the GitHub repository unixcrh/phuryn-pm-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 933 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to write-prd, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.