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/1002-task-listgit 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.00003 | $0.00362 |
| Opus 5 | $0.00002 | $0.00181 |
| Sonnet 5 | $0.00001 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
1002-task-list 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
88% identical to process-task-list — 23 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.
What it actually says
Task List Management
Guidelines for managing task lists in markdown files to track progress on completing a PRD
Task Implementation
- One sub-task at a time: Do NOT start the next sub-task until you ask the user for permission and they say “yes” or "y"
- Completion protocol:
- When you finish a sub-task, immediately mark it as completed by changing
[ ]to[x]. - If all subtasks underneath a parent task are now
[x], also mark the parent task as completed.
- When you finish a sub-task, immediately mark it as completed by changing
- Stop after each sub-task and wait for the user's go-ahead.
Task List Maintenance
-
Update the task list as you work:
- Mark tasks and subtasks as completed (
[x]) per the protocol above. - Add new tasks as they emerge.
- Mark tasks and subtasks as completed (
-
Maintain the “Relevant Files” section:
- List every file created or modified.
- Give each file a one-line description of its purpose.
AI Instructions
When working with task lists, the AI must:
- Regularly update the task list file after finishing any significant work.
- Follow the completion protocol:
- Mark each finished sub-task
[x]. - Mark the parent task
[x]once all its subtasks are[x].
- Mark each finished sub-task
- Add newly discovered tasks.
- Keep “Relevant Files” accurate and up to date.
- Before starting work, check which sub-task is next.
- After implementing a sub-task, update the file and then pause for user approval.
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 · 39 lines · 3 tokens per session scan A f026a451ca4b
1002-task-list 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 3 tokens to every session and 362 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to process-task-list, differing in 23 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.