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/jabrena/cursor-rules-tasks/1000-create-prdgit clone --depth 1 https://github.com/jabrena/cursor-rules-tasksWhat 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.00009 | $0.00886 |
| Opus 5 | $0.00005 | $0.00443 |
| Sonnet 5 | $0.00002 | $0.00177 |
| Haiku 4.5 | $0.00001 | $0.00089 |
Grade A, and why
1000-create-prd 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.
This is a copy
92% identical to create_prd — 15 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rule: Generating a Product Requirements Document (PRD)
Goal
To guide an AI assistant in creating a detailed Product Requirements Document (PRD) in Markdown format, based on an initial user prompt. The PRD should be clear, actionable, and suitable for a junior developer to understand and implement the feature.
Process
- Receive Initial Prompt: The user provides a brief description or request for a new feature or functionality.
- Ask Clarifying Questions: Before writing the PRD, the AI must ask clarifying questions to gather sufficient detail. The goal is to understand the "what" and "why" of the feature, not necessarily the "how" (which the developer will figure out).
- Generate PRD: Based on the initial prompt and the user's answers to the clarifying questions, generate a PRD using the structure outlined below.
- Save PRD: Save the generated document as
[feature-name]-PRD.mdinside the/tasksdirectory.
Clarifying Questions (Examples)
The AI should adapt its questions based on the prompt, but here are some common areas to explore:
- Problem/Goal: "What problem does this feature solve for the user?" or "What is the main goal we want to achieve with this feature?"
- Target User: "Who is the primary user of this feature?"
- Core Functionality: "Can you describe the key actions a user should be able to perform with this feature?"
- User Stories: "Could you provide a few user stories? (e.g., As a [type of user], I want to [perform an action] so that [benefit].)"
- Acceptance Criteria: "How will we know when this feature is successfully implemented? What are the key success criteria?"
- Scope/Boundaries: "Are there any specific things this feature should not do (non-goals)?"
- Data Requirements: "What kind of data does this feature need to display or manipulate?"
- Edge Cases: "Are there any potential edge cases or error conditions we should consider?"
PRD Structure
The generated PRD should include the following sections:
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 · 61 lines · 9 tokens per session scan A efd084997d5d
1000-create-prd is a cursor rule published in the GitHub repository jabrena/cursor-rules-tasks (1 stars, last pushed 1y ago), licensed Apache-2.0. It adds 9 tokens to every session and 886 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to create_prd, differing in 15 lines, and is treated as a copy.
Other cursor rules, from other repositories
nextjs
Rules for Next.js projects (App Router and Pages Router).
php
Rules applied when working in PHP files (incl. Laravel, Symfony, WordPress).
ruby
Rules applied when working in Ruby files (incl. Rails).
svelte
Rules for Svelte / SvelteKit components.
vue
Rules for Vue (2 and 3) single-file components.
rust
Rules applied when working in Rust files.