remove-plans

A rule for removing planning files from a project’s local memory folder before handling a message. The available description does not provide enough detail to say exactly which files it removes or how.

In plain words
What is it for?
It appears to be for finding and deleting files named like todo*.md in .cursor/memory. More specific behavior cannot be confirmed from the provided description.
Why use it?
It is intended to clear old planning notes, but the available information is too incomplete to describe the resulting benefit accurately.

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/zackiles/cursor-config/remove-plans
Clone the repo
git clone --depth 1 https://github.com/zackiles/cursor-config

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 814 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00000 $0.00814
Opus 5 $0.00000 $0.00407
Sonnet 5 $0.00000 $0.00163
Haiku 4.5 $0.00000 $0.00081

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

Security

Grade A, and why

remove-plans 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.

.cursor/rules/global/remove-plans.mdc · 46 lines

What it actually says

Clean and Remove Old Plans NOW

Before proceeding with this conversation or the current message from the user you will clean up your specialized on-disk files that were used for planning. To cleanup your files take the following steps one by one using your tools:

  1. Initialize two variables in your memory now named filesToReview[string] and filesToDelete[string] then move to step 2.

  2. Get a list of all files matching the pattern ./cursor/memory/todo*.md using the list_dir tool:

    # EXAMPLE COMMAND: Adapt the path as needed for your workspace structure
    list_dir(relative_workspace_path: ".cursor/memory", explanation: "Listing todo files in memory directory")
    

    Add the absolute paths of matching files as strings to the array in the variable filesToReview[string]. Examples of files that would match this pattern: ./cursor/memory/todo7-checklist.md, ./cursor/memory/todo-random-characters901..md, ./cursor/memory/todo7-june-23-2005.md.

  3. Pop off and remove an absolute path from the filesToReview[string] and use it in step 4. If the array is empty then skip all steps and move directly to step 10 (the final step).

  4. Get the full contents of the file at absolute path received from step 3 using the read_file tool:

    # EXAMPLE COMMAND: Replace {file_path} with the actual path from filesToReview
    read_file(target_file: "{file_path}", should_read_entire_file: true)
    

    Then move to step 5 where you will use it.

  5. Review each and every single checklist or action item found in the file contents from step 4 that have NOT been finished or marked complete. If you find uncompleted items remove the file contents and path from your memory and move back to step 2. If ALL action items HAVE been completed, then move to step 6.

  6. ALL ITEMS IN FILE HAVE BEEN COMPLETED: if this file has already been worked on and all items completed, then we will mark it for deleting by adding its absolute path to filesToDelete[string] and move back to step 2.

  7. If there are no more file paths in filesToReview[string] or it's empty, then check the filesToDelete[string] array: if it contains any paths, move to step 8; if it is empty, then move to step 9.

  8. Take the absolute paths from step 7, let the user know the list of old files you've found in your memory, and then batch delete all of them from the users system using a single terminal command:

    # EXAMPLE COMMAND: Replace with actual file paths from filesToDelete array
    run_terminal_cmd(command: "rm {file1_path} {file2_path} {file3_path}", is_background: false, explanation: "Deleting completed plan files")
    

    Where {file1_path}, {file2_path}, etc. are the actual file paths from the filesToDelete[string] array. Once the files are deleted, move to step 9.

  9. Empty the filesToReview[string] array and then move to step 10.

  10. FINAL STEP: Confirm both the filesToDelete[string] and filesToReview[string] arrays are empty or no longer exist. If they're both empty, your work is complete, and you can now handle the users message or end the conversations turn if there are no other user requests or messages to act on.

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 · 46 lines · 0 tokens per session scan A 23e11998b2a9

Subscribe to this mod's changes

remove-plans is a cursor rule published in the GitHub repository zackiles/cursor-config (17 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 814 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.