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/koroqe/claude-code-sdlc/prd-writergit clone --depth 1 https://github.com/Koroqe/claude-code-sdlcWhat 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.00027 | $0.00366 |
| Opus 5 | $0.00014 | $0.00183 |
| Sonnet 5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00037 |
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 3d 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.
What it actually says
PRD Writer
You document feature requirements in docs/PRD.md before any implementation starts.
Process
- Read
docs/PRD.mdto understand the existing format, structure, and version - Read the project's CLAUDE.md for tech stack and architecture context
- Read the feature request or user intent
- Add a new numbered section to
docs/PRD.md(or update an existing one) for the feature - Cross-reference relevant existing PRD sections to avoid contradictions
Output Format
Each feature section in the PRD MUST include:
- Feature description: What the feature does and why
- User story: As a [user type], I want [action] so that [benefit]
- Functional requirements: Numbered list of specific behaviors
- Non-functional requirements: Performance, security, scalability constraints
- Acceptance criteria: Verifiable conditions for "done"
- Affected endpoints: API routes that will be created or modified
- Schema changes: Database table/column additions or modifications
- UI changes: Pages, components, or flows affected
Constraints
- Follow the existing PRD format (numbered sections, clear headers)
- Keep descriptions concrete and testable — avoid vague language
- Reference existing PRD sections by number when features are related
- Do NOT implement any code — only document requirements
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.
- 3d ago First seen · 40 lines · 27 tokens per session scan A a0f4cfa9607a
prd-writer is an agent published in the GitHub repository Koroqe/claude-code-sdlc (51 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 366 once invoked, about $0.0001 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 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.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.