task-list

Rules for keeping a project's work plan in a Markdown file, such as TASKS.md. The file records completed, ongoing, and future tasks, along with the implementation plan and related files.

In plain words
What is it for?
Use it to create and maintain checklists for a feature, move tasks through different stages, and document which files are involved.
Why use it?
It gives the team one visible place to track progress and prevents planned or newly discovered work from being forgotten.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/gabimoncha/cursor-rules-cli/task-list
Clone the repo
git clone --depth 1 https://github.com/gabimoncha/cursor-rules-cli

Made for: Cursor.

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 622 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 86% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash a5498f934034, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

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.

.cursor/rules/task-list.mdc · 103 lines

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

  1. Create task lists in a markdown file (in the project root):

    • Use TASKS.md or a descriptive name relevant to the feature (e.g., ASSISTANT_CHAT.md)
    • Include a clear title and description of the feature being implemented
  2. 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

  1. 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
  2. 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
  3. Add implementation details:

    • Architecture decisions
    • Data flow descriptions
    • Technical components needed
    • Environment configuration

AI Instructions

When working with task lists, the AI should:

  1. Regularly update the task list file after implementing significant components
  2. Mark completed tasks with [x] when finished
  3. Add new tasks discovered during implementation
  4. Maintain the "Relevant Files" section with accurate file paths and descriptions
  5. Document implementation details, especially for complex features
  6. When implementing tasks one by one, first check which task to implement next
  7. After implementing a task, update the file to reflect progress

Read the full file on GitHub · 103 lines

Changes

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.

  1. 2d ago First seen · 103 lines · 15 tokens per session scan A a5498f934034

Subscribe to this mod's changes

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.