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 commands/fomo-driven-development/strategic-claude-base/prd.templategit clone --depth 1 https://github.com/Fomo-Driven-Development/strategic-claude-baseWrote 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/commands/fomo-driven-development/strategic-claude-base/prd.template)<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/prd.template"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/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 | $0.00000 | $0.01515 |
| Opus 5 | $0.00000 | $0.00758 |
| Sonnet 5 | $0.00000 | $0.00303 |
| Haiku 4.5 | $0.00000 | $0.00152 |
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 4d 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Requirements Document (PRD)
[Product/Feature Name]
Version [X.Y]
Date: [Current Date]
Status: [In Development/Planning/Review]
Executive Summary
[Brief 2-3 paragraph overview of what we're building, why it matters, and the expected impact. This should be accessible to both technical and non-technical stakeholders.]
Problem Statement
Current Challenges
[List the specific problems this product/feature solves]
- [Challenge Category]: [Detailed description of the problem]
- [Challenge Category]: [Detailed description of the problem]
- [Challenge Category]: [Detailed description of the problem]
User Pain Points
[Include real user quotes or scenarios that illustrate the problems]
- "[User quote expressing frustration or need]"
- "[Another user scenario or pain point]"
- "[Additional context about current limitations]"
Goals and Objectives
Primary Goals
[List 3-5 main goals this product will achieve]
- [Goal Category]: [Specific, measurable goal description]
- [Goal Category]: [Specific, measurable goal description]
- [Goal Category]: [Specific, measurable goal description]
Success Metrics
| Metric | Current | Target | Measurement |
|---|---|---|---|
| [Performance Metric] | [Current Value] | [Target Value] | [How to measure] |
| [Usage Metric] | [Current Value] | [Target Value] | [How to measure] |
| [Quality Metric] | [Current Value] | [Target Value] | [How to measure] |
| [User Satisfaction] | [Current Value] | [Target Value] | [How to measure] |
User Stories
[Primary User Persona]: [Name/Role]
Story 1: [Feature Area]
AS A [user type]
I WANT TO [action/capability]
SO THAT [benefit/outcome]
Acceptance Criteria:
- [Specific, testable criterion]
- [Specific, testable criterion]
- [Specific, testable criterion]
Story 2: [Feature Area]
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.
- 4d ago First seen · 272 lines · 0 tokens per session scan A aafaa1da68e3
PRD.template is a command published in the GitHub repository Fomo-Driven-Development/strategic-claude-base (2 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,515 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.