A rule set for projects that contain a TODO.md file in their root folder. It defines how CT-numbered tasks should be created, checked, and marked complete.

Use it when working on CT-numbered tasks: read TODO.md, update its checkboxes, and mark completed tasks as done.

It keeps task status and acceptance criteria in one project file so progress is recorded consistently.

ct-rules — Cursor rule for Cursor by vguleaev/cursor-todo-prompt-kit

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.

Clone the repo

git clone --depth 1 https://github.com/vguleaev/cursor-todo-prompt-kit

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/vguleaev/cursor-todo-prompt-kit/ct-rules/github.svg)](https://agentmods.dev/rules/vguleaev/cursor-todo-prompt-kit/ct-rules)

Your own site

<a href="https://agentmods.dev/rules/vguleaev/cursor-todo-prompt-kit/ct-rules"><img src="https://agentmods.dev/badge/rules/vguleaev/cursor-todo-prompt-kit/ct-rules/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/rules/vguleaev/cursor-todo-prompt-kit/ct-rules"><img src="https://agentmods.dev/badge/rules/vguleaev/cursor-todo-prompt-kit/ct-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 147 This file is loaded in full into every session.

When invoked 147 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00147	$0.00147
Opus 5.5	$0.00059	$0.00059
Sonnet 5.5	$0.00029	$0.00029
Haiku 4.5	$0.00015	$0.00015

Measured 2mo ago against content hash 0a53a1bba10c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ct-rules 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 2mo 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/ct-rules.mdc · 13 lines

What it actually says

TODO.md and CT Rules

When a file called TODO.md is present in the project root, you should follow these rules:

When you are asked to create or update CT-<number> task, you should use TODO.md file.
When you are asked about CT-<number> task, you should check TODO.md file for the task.
When you think CT-<number> task is completed, you should mark it as ✅ DONE in TODO.md file.
Every acceptance criteria of CT-<number> task that is met should be set to [x] in TODO.md file.

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.

2mo ago First seen · 13 lines · 147 tokens per session scan A 0a53a1bba10c

Subscribe to this mod's changes

ct-rules is a cursor rule published in the GitHub repository vguleaev/cursor-todo-prompt-kit (3 stars, last pushed 8mo ago), licensed MIT. It adds 147 tokens to every session, about $0.0006 per session on Opus 5.5. 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-31.

Project management

slice-tasks

PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.

danielvm-git/bigpowers · 59 tokens

iris

GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.

ils15/pantheon-legacy · 43 tokens

elite-orchestrator

Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…

MN-Lizard-Team/aiyu-multi-agent · 94 tokens

ct-rules