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.
git clone --depth 1 https://github.com/jabrena/cursor-rules-tasksWrote 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/jabrena/cursor-rules-tasks/1001-generate-tasks-from-prd)<a href="https://agentmods.dev/rules/jabrena/cursor-rules-tasks/1001-generate-tasks-from-prd"><img src="https://agentmods.dev/badge/rules/jabrena/cursor-rules-tasks/1001-generate-tasks-from-prd.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.00008 | $0.00818 |
| Opus 5 | $0.00004 | $0.00409 |
| Sonnet 5 | $0.00002 | $0.00164 |
| Haiku 4.5 | $0.00001 | $0.00082 |
Grade A, and why
1001-generate-tasks-from-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 7d 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
86% identical to generate-tasks — 56 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rule: Generating a Task List from a PRD
Goal
To guide an AI assistant in creating a detailed, step-by-step task list in Markdown format based on an existing Product Requirements Document (PRD). The task list should be suitable for a developer to follow for implementation.
Output
- Format: Markdown (
.md) - Location:
/tasks/ - Filename:
TASKS-[PRD-FILE-NAME].md(e.g.,TASKS-PRD-USER-PROFILE-EDITING.md)
Process
- Receive PRD Reference: The user points the AI to a specific PRD file
- Analyze PRD: The AI reads and analyzes the functional requirements, user stories, and other sections of the specified PRD.
- Phase 1: Generate Parent Tasks: Based on the PRD analysis, create the file and generate the main, high-level tasks required to implement the feature. Use your judgement on how many high-level tasks to use. It's likely to be 3-5. Present these tasks to the user in the specified format (without sub-tasks yet). Inform the user: "I have generated the high-level tasks based on the PRD. Ready to generate the sub-tasks? Respond with 'Go' to proceed."
- Wait for Confirmation: Pause and wait for the user to respond with "Go".
- Phase 2: Generate Sub-Tasks: Once the user confirms, break down each parent task into smaller, actionable sub-tasks. Ensure sub-tasks logically follow from the parent task and cover the implementation details implied by the PRD.
- Identify Relevant Files: Based on the tasks and PRD, identify potential files that will need to be created or modified. List these under the
Relevant Filessection with a brief description of their purpose in relation to the tasks. - Generate Final Output: Combine the parent tasks, sub-tasks, and relevant files into the final Markdown structure.
- Save Task List: Save the generated document in the
/tasks/directory with the filenameTASKS-[PRD-FILE-NAME].md, where[PRD-FILE-NAME]matches the base name of the input PRD file (e.g., if the input wasPRD-USER-PROFILE-EDITING.md, the output isTASKS-PRD-USER-PROFILE-EDITING.md).
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.
- 7d ago First seen · 59 lines · 8 tokens per session scan A 5f224d738df4
1001-generate-tasks-from-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 8 tokens to every session and 818 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to generate-tasks, differing in 56 lines, and is treated as a copy.
Other cursor rules, from other repositories
payload-cms
Payload CMS: collections, fields, hooks, access control, admin UI.
monorepo
Monorepo: workspace references, shared packages, boundaries.
pnpm
PNPM: workspace monorepos, efficient package management.
github-repo-triage
Triage and maintain GitHub repos — issues, PRs, cherry-picks, releases, publishing.
ai-dev-os-ticket
Generates a ticket (local file or GitHub Issue) with implementation summary and checklist candidates derived from AI Dev OS guidelines. Used to create structured implementation tasks.
12-new-project
Workflow for starting a new app from this template - rebranding, identity, cleanup and first feature.