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 skills add Dokkabei97/forged-claude-code --skill prd-writergit clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/skills/dokkabei97/forged-claude-code/prd-writer)<a href="https://agentmods.dev/skills/dokkabei97/forged-claude-code/prd-writer"><img src="https://agentmods.dev/badge/skills/dokkabei97/forged-claude-code/prd-writer.svg" alt="Measured on agentmods" 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.00056 | $0.01294 |
| Opus 5 | $0.00028 | $0.00647 |
| Sonnet 5 | $0.00011 | $0.00259 |
| Haiku 4.5 | $0.00006 | $0.00129 |
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 7d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Writer - Lightweight Product Requirements Document
Overview
Creates startup-appropriate PRDs — structured enough to align teams, lean enough to not slow you down. A good PRD answers "what and why", not "how".
1. When to Apply
| Trigger | Behavior |
|---|---|
| New feature planning | Generate full PRD template |
| "write PRD", "feature spec" | Guided PRD creation workflow |
| Before sprint planning | Quick PRD for prioritized features |
2. PRD Template
# PRD: [Feature Name]
> **Status**: Draft | In Review | Approved | In Development
> **Author**: [Name]
> **Date**: [YYYY-MM-DD]
> **Stakeholders**: [Names/Roles]
---
## 1. Problem Statement
[1-2 paragraphs. What problem are we solving? Who has this problem? How do they solve it today?]
**Evidence:**
- [User interview quote / data point / support ticket pattern]
- [Market research / competitor analysis finding]
## 2. Hypothesis
> If we [build X], then [target users] will [achieve Y],
> which we'll measure by [metric Z].
## 3. Success Metrics
| Metric | Current | Target | Measurement Method |
|--------|---------|--------|--------------------|
| Primary KPI | N/A or baseline | [target] | [how to measure] |
| Secondary KPI | N/A or baseline | [target] | [how to measure] |
| Guardrail Metric | [baseline] | [should not decrease] | [how to measure] |
## 4. Scope
### In Scope (MVP)
- [ ] [Core feature 1 — essential for value delivery]
- [ ] [Core feature 2 — essential for value delivery]
- [ ] [Core feature 3 — essential for value delivery]
### Out of Scope (Future)
- [Nice-to-have 1 — why deferred]
- [Nice-to-have 2 — why deferred]
### Non-Goals
- [What this feature explicitly will NOT do]
## 5. User Stories
### Primary Flow
> As a [user type], I want to [action], so that [benefit].
**Acceptance Criteria:**
- Given [context], when [action], then [result]
- Given [context], when [action], then [result]
### Secondary Flows
[Additional user stories as needed]
## 6. Design Considerations
- [UX principle or constraint]
- [Accessibility requirement]
- [Mobile/responsive considerations]
## 7. Technical Considerations
- [API changes needed]
- [Database schema impact]
- [Third-party integrations]
- [Performance requirements]
## 8. Edge Cases & Risks
| Edge Case | Expected Behavior |
|-----------|-------------------|
| [Edge case 1] | [How system should handle it] |
| [Edge case 2] | [How system should handle it] |
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| [Risk 1] | H/M/L | H/M/L | [Plan] |
## 9. Timeline
- **Target Start**: [Date]
- **Target Ship**: [Date]
- **Estimated Effort**: [S/M/L or story points]
## 10. Open Questions
- [ ] [Question that needs answering before development]
- [ ] [Question that needs answering before development]
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.
- 7d ago First seen · 187 lines · 56 tokens per session scan A d3e616784da1
prd-writer is a skill published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 56 tokens to every session and 1,294 once invoked, about $0.0003 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-31.
Other skills, from other repositories
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
telegram-setup
Connect a Telegram bot to the Vellum Assistant gateway with automated webhook registration and credential storage.
vellum-skills-catalog
Discover bundled skills and search/install community skills from the skills.sh registry.