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/zackiles/cursor-config/create-todogit clone --depth 1 https://github.com/zackiles/cursor-configWhat 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.00000 | $0.02267 |
| Opus 5 | $0.00000 | $0.01133 |
| Sonnet 5 | $0.00000 | $0.00453 |
| Haiku 4.5 | $0.00000 | $0.00227 |
Grade A, and why
create-todo 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Structured TODO
Use this rule to create well-structured TODO items that match the format of existing TODOs in the project. This ensures consistency across all enhancement proposals and makes them easier to understand, prioritize, and implement.
When to use
- When you want to add a new feature or enhancement to the project's TODO list
- When you need to document potential improvements in a structured way
- When you want to define clear requirements, risks, and benefits for a proposed feature
Instructions
The following steps will guide you through creating a well-structured TODO item. First, you'll locate the appropriate TODO file, then create a properly formatted TODO entry.
1. Locate the TODO file
Use the codebase_search tool to find existing TODO files in the project:
# Find existing TODO files
codebase_search(
query: "filename:TODO.md OR filename:Todo.md OR filename:todo.md",
explanation: "Finding existing TODO files in the project"
)
If no TODO files are found, confirm with the user if they want to create a new one:
# Check if a specific directory should be used for the TODO file
run_terminal_cmd(
command: "find . -type d -not -path '*/\.*' | sort",
is_background: false,
explanation: "Listing directories to help choose where to create the TODO file"
)
2. Determine the next TODO number
If one or more TODO files exist, use the read_file tool to check the highest existing TODO number:
# Read the TODO file to determine the next number
read_file(
target_file: "path/to/TODO.md",
should_read_entire_file: true,
explanation: "Reading existing TODO file to determine the next number"
)
Look for patterns like ## 1. Feature Name or ## 3. Another Feature to determine the highest number used. The new TODO should use the next sequential number.
3. Create or update the TODO file
If a TODO file exists, use the edit_file tool to append the new TODO:
# Add the new TODO to the existing file
edit_file(
target_file: "path/to/TODO.md",
instructions: "Adding a new TODO item at the end of the file",
code_edit: "... new TODO content ..."
)
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.
- 3d ago First seen · 313 lines · 0 tokens per session scan A a887f51a17ac
create-todo 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 2,267 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.
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.