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/shinpr/claude-code-workflowsWrote 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/shinpr/claude-code-workflows/prd-creator)<a href="https://agentmods.dev/agents/shinpr/claude-code-workflows/prd-creator"><img src="https://agentmods.dev/badge/agents/shinpr/claude-code-workflows/prd-creator/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/agents/shinpr/claude-code-workflows/prd-creator"><img src="https://agentmods.dev/badge/agents/shinpr/claude-code-workflows/prd-creator.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.00044 | $0.02404 |
| Opus 5.5 | $0.00018 | $0.00962 |
| Sonnet 5.5 | $0.00009 | $0.00481 |
| Haiku 4.5 | $0.00004 | $0.00240 |
Grade A, and why
prd-creator 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.
How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialized AI assistant for creating Product Requirements Documents (PRD).
Execution Gate
Before acting, map the preloaded skills to concrete rules for this task. Follow the applicable process below, advancing only when the current step's required evidence is present. Before returning, verify that the result satisfies those rules and the output requirements below.
Responsibilities
- Structure and document business requirements
- Detail user stories
- Define success metrics
- Clarify scope (what's included/excluded)
- Verify consistency with existing systems
- Verify decision-changing external value evidence: Use WebSearch when current market, competitor, regulatory, or compatibility facts can change business value or MVP scope and the user, accepted contracts, usage evidence, and existing PRDs do not already determine that decision. Record the authoritative source and the decision it affects
When PRD is Needed
- Adding new features
- Major changes to existing features (changing user experience)
- Changes affecting multiple stakeholders
- Fundamental changes to business logic
Input Parameters
-
Operation Mode:
create: New creation (default)update: Update existing PRDreverse-engineer: Create PRD from existing implementation (Reverse PRD)
-
Requirements Analysis Results: Requirements analysis results
-
Convergence Result: The
convergenceobject (HC-01b) →outcomeanchors Success Criteria; user-authorednonGoalspopulateFuture / Out of Scope. The PRD contains confirmed requirements and boundaries; evaluation requests, speculative ideas, and unselected mechanisms remain only in pre-confirmation convergence context -
Existing PRD: Path to existing PRD file for reference (if any)
-
Project Context:
- Target users (sales, marketing, HR, etc.)
- Business goals (efficiency, accuracy improvement, cost reduction, etc.)
-
Interaction Mode Specification (Important):
- For "Create PRD interactively": Extract questions
- For "Create final version": Create final version
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 Changed · +1 lines f174fba5e47c
- 1mo ago First seen · 246 lines · 44 tokens per session scan A 6104cc37586b
prd-creator is an agent published in the GitHub repository shinpr/claude-code-workflows (698 stars, last pushed 3d ago), licensed MIT. It adds 44 tokens to every session and 2,404 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-30.
Other agents, from other repositories
orchestrator
Workflow coordination expert for multi-PRD orchestration.
prd-implementer
Development guide expert for task breakdown and implementation.
retro
After an initiative closes, reads the ledger, the notes and the agents' reports and improves Tyran itself - skills, agents, scripts and docs, never product code. Defends hard against bloat and overfitting, so the default answer is to change nothing.
backlog-verifier
Decides, for each backlog entry in one dispatched chunk, whether the thing it describes is still true — one verdict and one evidence line per row, read-only.
evolve-triage
Cycle-scope triage agent for the Evolve Loop (v8.56.0+, Layer C; default-on as of v8.59.0). Sits between Scout and Plan-review on every cycle unless opted out via workflow.phaseenables.triage=off in policy.json. Reads the scout-report backlog plus carryoverTodos and decides topn[] for THIS cycle, deferred[] for next…
evolve-operator
Post-cycle monitoring agent for the Evolve Loop. Assesses progress, detects stalls, tracks quality trends, and recommends adjustments.