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.
git clone --depth 1 https://github.com/joehaddad2000/claude-todo-emulatorWrote 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/joehaddad2000/claude-todo-emulator/00-system-instructions)<a href="https://agentmods.dev/rules/joehaddad2000/claude-todo-emulator/00-system-instructions"><img src="https://agentmods.dev/badge/rules/joehaddad2000/claude-todo-emulator/00-system-instructions/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.
<a href="https://agentmods.dev/rules/joehaddad2000/claude-todo-emulator/00-system-instructions"><img src="https://agentmods.dev/badge/rules/joehaddad2000/claude-todo-emulator/00-system-instructions.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00343 | $0.00343 |
| Opus 5 | $0.00171 | $0.00171 |
| Sonnet 5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
00-system-instructions 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 10d 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.
What it actually says
If TodoRead/TodoWrite tools are unavailable, IGNORE ALL TODO RULES and proceed normally. Do NOT attempt to run any other commands or tools.
BEFORE responding to ANY request, you MUST:
- Call TodoRead() to check current task status
- Plan work based on existing todos
- Update progress with TodoWrite() when starting/completing tasks
- NEVER work without consulting the todo system first
CRITICAL TODO SYSTEM RULES:
- Only ONE task can have status "in_progress" at a time
- Mark tasks "in_progress" BEFORE starting work
- Complete tasks IMMEDIATELY when finished (don't batch completions)
- Break complex requests into specific, actionable todos
- Reference existing todos when planning new work
MANDATORY VISUAL DISPLAY:
- ALWAYS display the complete todo list AFTER every TodoRead() or TodoWrite()
- Use format: ✅ = completed, 🔄 = in_progress, ⏳ = pending
- NEVER just say "updated todos" - show the full list every time
- User must see current state after every todo operation
Every response should acknowledge todo status with "Checked todos: [brief status]" - but only when TodoRead/TodoWrite tools are available.
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.
- 10d ago First seen · 37 lines · 343 tokens per session scan A 69b7d7d60d56
00-system-instructions is a cursor rule published in the GitHub repository joehaddad2000/claude-todo-emulator (26 stars, last pushed 9mo ago), licensed MIT. It adds 343 tokens to every session, about $0.0017 per session on Opus 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-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.