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 agentmods add skills/yezannnnn/agentgroup/prd-templatenpx skills add yezannnnn/agentGroup --skill prd-templategit clone --depth 1 https://github.com/yezannnnn/agentGroupWrote 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/yezannnnn/agentgroup/prd-template)<a href="https://agentmods.dev/skills/yezannnnn/agentgroup/prd-template"><img src="https://agentmods.dev/badge/skills/yezannnnn/agentgroup/prd-template.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.00052 | $0.01200 |
| Opus 5 | $0.00026 | $0.00600 |
| Sonnet 5 | $0.00010 | $0.00240 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
prd-template 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 2d 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
1 near-identical copy found in the catalogue:
- prd-template — 86% identical, 29 lines differ
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Template Skill
This skill helps create professional Product Requirements Documents following industry best practices.
Template Structure
Every PRD should include these sections in order:
1. Overview
- Problem Statement: What problem are we solving? (2-3 sentences)
- Proposed Solution: High-level description of what we're building (2-3 sentences)
- Success Metrics: How we'll measure success (3-5 key metrics)
2. Context & Background
- Why Now: Why is this the right time?
- Strategic Alignment: How does this align with company objectives?
- User Research Summary: Key insights from research (if applicable)
3. User Stories & Use Cases
Format: "As a [user type], I want to [action] so that [benefit]"
- Include 3-7 primary user stories
- Add acceptance criteria for each
4. Requirements
Functional Requirements:
- Must-have features (P0)
- Should-have features (P1)
- Nice-to-have features (P2)
Non-Functional Requirements:
- Performance expectations
- Security considerations
- Accessibility requirements
5. Design & User Experience
- Link to design mocks or wireframes
- Key user flows
- Edge cases and error states
6. Technical Considerations
- Architecture implications
- Dependencies on other systems
- Technical risks and mitigations
7. Implementation Plan
- Phase 1 (MVP): What goes in first version
- Phase 2: What comes next
- Phase 3: Future enhancements
8. Open Questions
- Decisions that still need to be made
- Stakeholders to consult
- Research needed
9. Appendix
- Research links
- Related documents
- Competitive analysis
Writing Guidelines
Tone: Clear, concise, actionable Audience: Engineers, designers, stakeholders Length: Aim for 3-6 pages for features, 8-12 for products
Best Practices:
- Use concrete examples over abstractions
- Include "why" not just "what"
- Make requirements testable
- Link to supporting materials
- Update as decisions are made
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.
- 2d ago First seen · 145 lines · 52 tokens per session scan A 92052aa196fc
prd-template is a skill published in the GitHub repository yezannnnn/agentGroup (149 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 1,200 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-09-03.
Other skills, from other repositories
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.