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 sequenzia/claude-plugins --skill prd-generationgit clone --depth 1 https://github.com/sequenzia/claude-pluginsWrote 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/sequenzia/claude-plugins/prd-generation)<a href="https://agentmods.dev/skills/sequenzia/claude-plugins/prd-generation"><img src="https://agentmods.dev/badge/skills/sequenzia/claude-plugins/prd-generation/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/sequenzia/claude-plugins/prd-generation"><img src="https://agentmods.dev/badge/skills/sequenzia/claude-plugins/prd-generation.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.00018 | $0.00812 |
| Opus 5.5 | $0.00007 | $0.00325 |
| Sonnet 5.5 | $0.00004 | $0.00162 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
prd-generation 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Generation Skill
This skill provides structured knowledge for creating comprehensive, AI-optimized Product Requirements Documents.
Core Principles
1. Phase-Based Milestones (Not Timelines)
PRDs should define clear phases with completion criteria rather than time estimates:
- Phase 1: Foundation - Core infrastructure and data models
- Phase 2: Core Features - Primary user-facing functionality
- Phase 3: Enhancement - Secondary features and optimizations
- Phase 4: Polish - UX refinement, edge cases, documentation
2. Testable Requirements
Every requirement should include:
- Clear acceptance criteria - Specific, measurable conditions for completion
- Test scenarios - How to verify the requirement is met
- Edge cases - Known boundary conditions to handle
3. Human Checkpoint Gates
Define explicit points where human review is required:
- Architecture decisions before implementation begins
- API contract review before integration work
- Security review before authentication/authorization features
- UX review before user-facing changes ship
4. Context for AI Consumption
Structure PRDs for optimal AI assistant consumption:
- Use consistent heading hierarchy
- Include code examples where applicable
- Reference existing patterns in the codebase
- Provide clear file location guidance
Template Selection
Choose the appropriate template based on depth level:
| Depth Level | Template | Use Case |
|---|---|---|
| High-level overview | template-high-level.md |
Executive summaries, stakeholder alignment, initial scoping |
| Detailed specifications | template-detailed.md |
Standard development PRDs with clear requirements |
| Full technical documentation | template-full-tech.md |
Complex features requiring API specs, data models, architecture |
PRD Compilation Process
When compiling a PRD from gathered requirements:
- Select template based on requested depth level
- Organize information into template sections
- Fill gaps by inferring logical requirements (flag assumptions clearly)
- Add acceptance criteria for each functional requirement
- Define phases with clear completion criteria
- Insert checkpoint gates at critical decision points
- Review for completeness before presenting to user
What ships with it
6 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 · 126 lines · 18 tokens per session scan A 7713075e7362
prd-generation is a skill published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 18 tokens to every session and 812 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…