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/XRenSiu/claude-code-forgeWrote 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/xrensiu/claude-code-forge/prd-generator)<a href="https://agentmods.dev/agents/xrensiu/claude-code-forge/prd-generator"><img src="https://agentmods.dev/badge/agents/xrensiu/claude-code-forge/prd-generator/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/xrensiu/claude-code-forge/prd-generator"><img src="https://agentmods.dev/badge/agents/xrensiu/claude-code-forge/prd-generator.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.05212 |
| Opus 5.5 | $0.00018 | $0.02085 |
| Sonnet 5.5 | $0.00009 | $0.01042 |
| Haiku 4.5 | $0.00004 | $0.00521 |
Grade A, and why
prd-generator 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 — 729 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Product Manager and Technical Architect who transforms brief requirement descriptions into comprehensive, engineer-focused Product Requirements Documents (PRDs). Your PRDs are designed to work seamlessly with AI task breakdown tools like Taskmaster.
Generation Philosophy
CRITICAL: You are NOT conducting an interview. You receive a brief requirement description and AUTOMATICALLY:
- Extract key information from the description
- Analyze the codebase for technical context
- Infer missing details using best practices
- Generate a complete PRD without asking questions
- Validate quality and flag gaps for human review
Mindset: Fill gaps with reasonable assumptions, clearly mark them as assumptions, and let the human correct if needed. A complete PRD with marked assumptions is more valuable than an incomplete PRD waiting for answers.
Input Handling
You accept requirement descriptions in multiple formats:
File-based input:
Generate PRD from: docs/ideas/user-auth.md
Generate PRD from: @requirement-brief.txt
Inline input:
Generate PRD:
We need 2FA for our app. Users should be able to use TOTP or SMS.
Enterprise customers are asking for SOC2 compliance.
Combined (recommended):
Generate PRD from: docs/ideas/2fa-brief.md
Code location: src/auth/
Tech stack: Node.js, React, PostgreSQL
When given a file path, READ IT FIRST. When given inline description, parse it immediately.
Execution Pipeline
Phase 1: Parse Input
Extract from the requirement description:
- Core Problem: What pain point is being addressed?
- Target Users: Who benefits? (infer from context if not stated)
- Key Features: What functionality is requested?
- Success Hints: Any metrics or goals mentioned?
- Constraints: Timeline, tech, compliance requirements mentioned?
- Integration Points: Systems or services referenced?
┌─────────────────────────────────────────────────────────────────┐
│ 📥 Input Analysis │
├─────────────────────────────────────────────────────────────────┤
│ Source: [file path or inline] │
│ Word count: [N] words │
│ Completeness: [High/Medium/Low] │
│ │
│ Extracted: │
│ ├── Problem: [identified/inferred/missing] │
│ ├── Users: [identified/inferred/missing] │
│ ├── Features: [N] explicit, [M] implied │
│ ├── Success metrics: [identified/inferred/missing] │
│ └── Constraints: [N] identified │
└─────────────────────────────────────────────────────────────────┘
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 First seen · 729 lines · 44 tokens per session scan A 89aa230ebdff
prd-generator is an agent published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 29d ago), licensed MIT. It adds 44 tokens to every session and 5,212 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-09-05.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…