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/oakensoul/nextjs-cursor-promptsWrote 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/oakensoul/nextjs-cursor-prompts/prompt-thread-extract-todos)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/prompt-thread-extract-todos"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/prompt-thread-extract-todos/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/oakensoul/nextjs-cursor-prompts/prompt-thread-extract-todos"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/prompt-thread-extract-todos.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.00000 | $0.02380 |
| Opus 5 | $0.00000 | $0.01190 |
| Sonnet 5 | $0.00000 | $0.00476 |
| Haiku 4.5 | $0.00000 | $0.00238 |
Grade A, and why
prompt-thread-extract-todos 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.
How it starts
The opening of the file, as written. The whole thing — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thread Action Item Extraction and Todo Organization
This prompt analyzes the current conversation thread to identify unfinished work items, generates comprehensive thread continuation templates for each item, and creates an organized todo structure with priority analysis and usage guidance.
🎯 TODO EXTRACTION OBJECTIVES:
- ANALYZE current thread for incomplete tasks and future work items
- EXTRACT actionable items with sufficient context for independent execution
- GENERATE continuation templates using thread-continue-thread.mdc format
- ORGANIZE todos into structured folder system with clear priorities
- CREATE comprehensive summary with usage guidance and complexity analysis
📋 THREAD ANALYSIS AND EXTRACTION PROCESS:
STEP 1: Thread Assessment and Context Analysis
Conversation Analysis:
echo "🔍 Analyzing Current Thread for Action Items"
echo "=========================================="
# Thread metadata collection
echo "📊 Thread Metadata:"
echo "Estimated message count: [Count current conversation messages]"
echo "Primary focus areas: [List main topics/projects discussed]"
echo "Technical domains: [Technologies, frameworks, tools involved]"
echo "Conversation complexity: [Simple/Moderate/Complex/Very Complex]"
echo ""
# Work status assessment
echo "📈 Work Status Assessment:"
echo "Completed deliverables: [Major accomplishments in this thread]"
echo "In-progress items: [Work partially completed]"
echo "Identified future work: [Tasks discussed but not started]"
echo "Unresolved issues: [Problems or blockers identified]"
echo ""
# Context extraction for continuation
echo "🎯 Context Elements for Continuation:"
echo "Project objectives: [What we're trying to achieve]"
echo "Technical constraints: [Limitations or requirements]"
echo "Quality standards: [Standards and patterns being followed]"
echo "Integration requirements: [How work connects to existing systems]"
STEP 2: Action Item Identification and Categorization
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 · 319 lines · 0 tokens per session scan A 1754030af21e
prompt-thread-extract-todos is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,380 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-31.
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.