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/gabimoncha/cursor-rules-cli/task-listgit clone --depth 1 https://github.com/gabimoncha/cursor-rules-cliWhat 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.00015 | $0.00622 |
| Opus 5 | $0.00008 | $0.00311 |
| Sonnet 5 | $0.00003 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
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
86% identical to task — 33 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guidelines for creating and managing task lists in markdown files to track project progress
Task List Creation
-
Create task lists in a markdown file (in the project root):
- Use
TASKS.mdor a descriptive name relevant to the feature (e.g.,ASSISTANT_CHAT.md) - Include a clear title and description of the feature being implemented
- Use
-
Structure the file with these sections:
# Feature Name Implementation Brief description of the feature and its purpose. ## Completed Tasks - [x] Task 1 that has been completed - [x] Task 2 that has been completed ## In Progress Tasks - [ ] Task 3 currently being worked on - [ ] Task 4 to be completed soon ## Future Tasks - [ ] Task 5 planned for future implementation - [ ] Task 6 planned for future implementation ## Implementation Plan Detailed description of how the feature will be implemented. ### Relevant Files - path/to/file1.ts - Description of purpose - path/to/file2.ts - Description of purpose
Task List Maintenance
-
Update the task list as you progress:
- Mark tasks as completed by changing
[ ]to[x] - Add new tasks as they are identified
- Move tasks between sections as appropriate
- Mark tasks as completed by changing
-
Keep "Relevant Files" section updated with:
- File paths that have been created or modified
- Brief descriptions of each file's purpose
- Status indicators (e.g., ✅) for completed components
-
Add implementation details:
- Architecture decisions
- Data flow descriptions
- Technical components needed
- Environment configuration
AI Instructions
When working with task lists, the AI should:
- Regularly update the task list file after implementing significant components
- Mark completed tasks with [x] when finished
- Add new tasks discovered during implementation
- Maintain the "Relevant Files" section with accurate file paths and descriptions
- Document implementation details, especially for complex features
- When implementing tasks one by one, first check which task to implement next
- After implementing a task, update the file to reflect progress
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 · 103 lines · 15 tokens per session scan A a5498f934034
task-list is a cursor rule published in the GitHub repository gabimoncha/cursor-rules-cli (50 stars, last pushed 1y ago), licensed MIT. It adds 15 tokens to every session and 622 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to task, differing in 33 lines, and is treated as a copy.
Other cursor rules, from other repositories
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.