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 hamzafarooq/claude-code-starter --skill prd-generatorgit clone --depth 1 https://github.com/hamzafarooq/claude-code-starterWrote 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/hamzafarooq/claude-code-starter/prd-generator)<a href="https://agentmods.dev/skills/hamzafarooq/claude-code-starter/prd-generator"><img src="https://agentmods.dev/badge/skills/hamzafarooq/claude-code-starter/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/skills/hamzafarooq/claude-code-starter/prd-generator"><img src="https://agentmods.dev/badge/skills/hamzafarooq/claude-code-starter/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.00030 | $0.00513 |
| Opus 5.5 | $0.00012 | $0.00205 |
| Sonnet 5.5 | $0.00006 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00051 |
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.
What it actually says
What this skill does
When triggered, ask the user for:
- Feature name (one line)
- Problem being solved (1-3 sentences)
- Target user(s)
- Any known constraints or context (timeline, technical limits, compliance, etc.)
Then generate a full PRD using the structure below.
PRD Structure
1. Problem Statement
What pain are we solving and for whom? Why does this matter now?
2. Goals
3-5 measurable outcomes we want to achieve with this feature. Format: "Increase [metric] by [amount] within [timeframe]"
3. Non-Goals
What this feature explicitly will NOT do. Be specific. This section prevents scope creep.
4. Users & Use Cases
Who uses this feature and in what context? Include 2-3 concrete scenarios (short narrative, not bullets).
5. User Stories
Written as: "As a [user type], I want to [action] so that [outcome]." Group into: Must-have / Should-have / Nice-to-have
6. Acceptance Criteria
Written in Given/When/Then format for each must-have story. Should be specific enough that a QA engineer can write a test.
7. Risks & Assumptions
Two columns:
- Risks — What could go wrong? What dependencies exist?
- Assumptions — What are we treating as true that we haven't confirmed?
8. Open Questions
What must be decided before engineering starts? Format as questions, not statements. Assign an owner if known.
9. Success Metrics
How will we measure whether this feature succeeded? Include leading indicators (early signals) and lagging indicators (final outcomes).
How to respond
- Write the full PRD directly — do not explain what you're about to write
- Use plain English — avoid technical jargon
- Mark any section where you made an assumption with
[ASSUMPTION] - Mark anything that needs the PM's input with
[NEEDS INPUT] - End with: "Review the [ASSUMPTION] and [NEEDS INPUT] sections before sharing with engineering."
- Ask the user if they want to save it to
docs/prd.md
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 · 66 lines · 30 tokens per session scan A a2ce10d1c23a
prd-generator is a skill published in the GitHub repository hamzafarooq/claude-code-starter (145 stars, last pushed 7d ago), licensed MIT. It adds 30 tokens to every session and 513 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-09-03.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
remove
Remove a deployed framework or addon from the current workspace.