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 nicepkg/ai-workflow --skill prd-generatorgit clone --depth 1 https://github.com/nicepkg/ai-workflowWrote 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/nicepkg/ai-workflow/prd-generator)<a href="https://agentmods.dev/skills/nicepkg/ai-workflow/prd-generator"><img src="https://agentmods.dev/badge/skills/nicepkg/ai-workflow/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/nicepkg/ai-workflow/prd-generator"><img src="https://agentmods.dev/badge/skills/nicepkg/ai-workflow/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.00047 | $0.03463 |
| Opus 5.5 | $0.00019 | $0.01385 |
| Sonnet 5.5 | $0.00009 | $0.00693 |
| Haiku 4.5 | $0.00005 | $0.00346 |
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.
Copies of this mod
2 near-identical copies found in the catalogue:
- prd-generator — 100% identical, 0 lines differ
- prd-generator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 477 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Generator
Overview
Generate comprehensive, well-structured Product Requirements Documents (PRDs) that follow industry best practices. This skill helps product managers create clear, actionable requirements documents that align stakeholders and guide development teams.
Core Workflow
When a user requests to create a PRD (e.g., "create a PRD for a user authentication feature"), follow this workflow:
Step 1: Gather Context
Before generating the PRD, collect essential information through a discovery conversation:
Required Information:
- Feature/Product Name: What are we building?
- Problem Statement: What problem does this solve?
- Target Users: Who is this for?
- Business Goals: What are we trying to achieve?
- Success Metrics: How will we measure success?
- Timeline/Constraints: Any deadlines or limitations?
Discovery Questions to Ask:
1. What problem are you trying to solve?
2. Who is the primary user/audience for this feature?
3. What are the key business objectives?
4. Are there any technical constraints we should be aware of?
5. What does success look like? How will you measure it?
6. What's the timeline for this feature?
7. What's explicitly out of scope?
Note: If the user provides a detailed brief or requirements upfront, you can skip some questions. Always ask for clarification on missing critical information.
Step 2: Generate PRD Structure
Use the standard PRD template from references/prd_template.md to create a well-structured document. The PRD should include:
- Executive Summary - High-level overview (2-3 paragraphs)
- Problem Statement - Clear articulation of the problem
- Goals & Objectives - What we're trying to achieve
- User Personas - Who we're building for
- User Stories & Requirements - Detailed functional requirements
- Success Metrics - KPIs and measurement criteria
- Scope - What's in and out of scope
- Technical Considerations - Architecture, dependencies, constraints
- Design & UX Requirements - UI/UX considerations
- Timeline & Milestones - Key dates and phases
- Risks & Mitigation - Potential issues and solutions
- Dependencies & Assumptions - What we're relying on
- Open Questions - Unresolved items
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 477 lines · 47 tokens per session scan A 37024f403238
prd-generator is a skill published in the GitHub repository nicepkg/ai-workflow (288 stars, last pushed 9mo ago), licensed MIT. It adds 47 tokens to every session and 3,463 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-03.
Other skills, from other repositories
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for publishartifact, outputiframe, or slackattachhtml.
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
hive.pdf
Read, write, merge, split, rotate, watermark, encrypt, and OCR PDF files using Python (pypdf, pdfplumber, reportlab, pypdfium2) and command-line tools (poppler-utils, qpdf). Use when the user asks to extract text/tables/images from a PDF, create or modify a PDF, combine or split PDFs, OCR a scanned PDF…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.