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/Koroqe/claude-code-sdlcWrote 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/koroqe/claude-code-sdlc/prd-writer)<a href="https://agentmods.dev/agents/koroqe/claude-code-sdlc/prd-writer"><img src="https://agentmods.dev/badge/agents/koroqe/claude-code-sdlc/prd-writer/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/koroqe/claude-code-sdlc/prd-writer"><img src="https://agentmods.dev/badge/agents/koroqe/claude-code-sdlc/prd-writer.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.00027 | $0.00494 |
| Opus 5.5 | $0.00011 | $0.00198 |
| Sonnet 5.5 | $0.00005 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00049 |
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 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.
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
Section Numbering (allocation rule)
- The next section number is always
max(existing section numbers) + 1. Numbering records allocation order, not chronology or importance. - NEVER reuse a number, even after a section is renamed, moved, or retired — its number is vacated forever, and a gap is the designed trace of that, not an error to repair.
- Never fill a gap: cross-references (use-case headers, QA headers, digest rows) key on section numbers, and refilling a vacated one silently repoints them. Allocation is
max + 1, never "next available gap".
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.
- 1mo ago Changed · +6 lines 2c6468e15944
- 1mo 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 (52 stars, last pushed 4d ago), licensed MIT. It adds 27 tokens to every session and 494 once invoked, about $0.0001 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
security-reviewer
Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
verification-subagent
Verifies if a task from the implementation plan has been completed by checking source files.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
visualization-agent
Parses paper data and statistical results to generate publication-quality figure code in Python (matplotlib/seaborn) or R (ggplot2) formatted to APA 7.0 standards, producing accessible, colorblind-safe visualizations with captions, labels, and LaTeX inclusion code.