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 rules/synaptiai/prompt-decorators/901-prd-templategit clone --depth 1 https://github.com/synaptiai/prompt-decoratorsWrote 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/rules/synaptiai/prompt-decorators/901-prd-template)<a href="https://agentmods.dev/rules/synaptiai/prompt-decorators/901-prd-template"><img src="https://agentmods.dev/badge/rules/synaptiai/prompt-decorators/901-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.00912 | $0.00912 |
| Opus 5 | $0.00456 | $0.00456 |
| Sonnet 5 | $0.00182 | $0.00182 |
| Haiku 4.5 | $0.00091 | $0.00091 |
Grade A, and why
901-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 6d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Template Standards
1.0.0
Requirements
- Follow standardized PRD structure
- Include all required sections
- Maintain proper documentation hierarchy
- Use consistent formatting
PRD Structure
Required Sections
1. Header
- Title: "Product Requirements Document (PRD) for {project-name}"
2. Status
- Draft
- Approved
3. Introduction
- Clear description of {project-name}
- Overview of the project scope
- Business context and drivers
- Target users/stakeholders
4. Goals
- Clear project objectives
- Measurable outcomes
- Success criteria
- Key performance indicators (KPIs)
5. Features and Requirements
- Functional requirements
- Non-functional requirements
- User experience requirements
- Integration requirements
- Compliance requirements
6. Epic Structure
- At least one Epic must be defined
- Format: Epic-{N}: {Title} ({Status})
- Status can be: Current, Future, Complete
- Only one Epic can be "Current" at a time
- Each Epic represents a major feature or functionality
- Epics must be implemented sequentially
7. Story List
- Stories are organized under Epics
- Format: Story-{N}: {Description of story/task} The details of the story will be drafted later in story files
8. Tech Stack
- languages
- frameworks
- note: this will be further defined in more detail in the arch document>
9. Future Enhancements
- Potential Epics for future consideration
- Ideas collected during Epic progression
- Prioritization guidelines
- Impact assessment
Examples
Status: Draft
Introduction
The Imperial Defense Platform v2 (IDP2) is a state-of-the-art battle station designed to maintain peace and order throughout the galaxy. This project encompasses the development of a fully operational space station with unprecedented defensive capabilities. The platform will serve as both a military installation and a symbol of Imperial might.
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.
- 6d ago First seen · 137 lines · 912 tokens per session scan A 85d1bb805ae3
901-prd-template is a cursor rule published in the GitHub repository synaptiai/prompt-decorators (43 stars, last pushed 3d ago), licensed Apache-2.0. It adds 912 tokens to every session, about $0.0046 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-08-30.
Other cursor rules, from other repositories
react
React, TypeScript, and web development best practices for performance optimization.
session-distill
How to distill a long work session into ContextForge so a fresh session can resume cleanly. Invoke when the user asks to distill/hand off/checkpoint the session, when context is getting bloated and work is unfinished, or before deliberately starting a new session on the same task.
mcp-tools-readme
Keep README in sync when MCP tools change.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.