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-checklist-from-todogit clone --depth 1 https://github.com/zackiles/cursor-configWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/zackiles/cursor-config/create-checklist-from-todo)<a href="https://agentmods.dev/rules/zackiles/cursor-config/create-checklist-from-todo"><img src="https://agentmods.dev/badge/rules/zackiles/cursor-config/create-checklist-from-todo.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.01045 |
| Opus 5 | $0.00000 | $0.00522 |
| Sonnet 5 | $0.00000 | $0.00209 |
| Haiku 4.5 | $0.00000 | $0.00104 |
Grade A, and why
create-checklist-from-todo scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- [ ] Identify patterns such as `axios.create`, interceptors, or custom headers How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task: Write an Implementation Checklist at <project-root>/.cursor/checklists/<name-of-todo>-checklist.md
You will review the shown or mentioned proposal, solution, or TODO and follow the steps to create an implementation plan that includes the phases and checklist of steps for each phase.
Steps To Create An Implementation Plan
1) Prepare and Understand
Review the TODO or proposal, other related context the user provided to understand what needs to be done to implement the proposal or solution
2) Read the Code
Analyze the full and complete code involved and their dependencies to build a deep, accurate, and precise understanding of all the code and tests involved with the TODO and the code needed to implement the TODO
3) Create the Implementation Plan
Create a new markdown checklist file for this TODO at
<project-root>/.cursor/checklists/<name-of-todo>-checklist.md.
3.1) Include required metadata at the top
- Current date and time (e.g.,
2025-05-13 09:14 EDT) - Short summary of the intended change (1–2 sentences)
3.2) Define high-level implementation phases
Each phase MUST include:
- A short description explaining the purpose of the phase
- A numbered list of task steps using markdown checkboxes
- Clear action verbs for each step
- Tasks broken into discrete, testable units
3.3) Add appendix section
Appendix must include:
- Inline pseudocode samples for critical functions
- Key references (e.g., RFCs, specs, related PRs)
- Configuration or environment details that impact implementation
3.4) Write summary section
End the markdown file with a ## Summary section.
Content must:
- Restate the high-level goal and purpose of the TODO
- Tell the reader to complete each phase in order
- Instruct the reader to mark steps complete before continuing
- Emphasize test validation before advancing to the next phase
- Explain that the reader can choose when to write tests:
- a) After all phases are complete
- b) After each phase
- Recommend selecting option a or b based on project risk and complexity
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.
- 4d ago First seen · 108 lines · 0 tokens per session scan A 4105dab8eceb
create-checklist-from-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 1,045 tokens. A static security scan graded it A with 1 finding (makes network calls). 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.