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/oakensoul/nextjs-cursor-prompts/prompt-continue-threadgit 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-continue-thread)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/prompt-continue-thread"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/prompt-continue-thread.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.1 | $0.00000 | $0.02656 |
| Opus 5 | $0.00000 | $0.01328 |
| Sonnet 5 | $0.00000 | $0.00531 |
| Haiku 4.5 | $0.00000 | $0.00266 |
Grade A, and why
prompt-continue-thread 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 6d 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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thread Continuation and Context Transfer
This prompt enables seamless context transfer between conversation threads by creating comprehensive summaries of completed work and identifying unfinished tasks, ensuring continuity and preventing loss of progress.
🎯 THREAD CONTINUATION OBJECTIVES:
- SUMMARIZE accomplished tasks and deliverables from current thread
- IDENTIFY unfinished work and next steps requiring continuation
- EXTRACT key decisions and important context for new thread
- DOCUMENT project state with actionable handoff information
- PROVIDE transition template for starting new thread effectively
📋 THREAD ANALYSIS AND CONTINUATION:
STEP 1: Thread Context Analysis
Conversation Overview Assessment:
echo "🔍 Analyzing Thread Context for Continuation"
echo "==========================================="
# Thread metadata analysis
echo "📊 Thread Analysis Summary:"
echo "Thread length: [Estimated message count]"
echo "Duration: [Time span of conversation]"
echo "Primary focus: [Main topic/project being worked on]"
echo "Complexity level: [Simple/Moderate/Complex/Highly Complex]"
echo ""
# Identify conversation phases
echo "📈 Conversation Phases Identified:"
echo "1. Initial Problem/Request Definition"
echo "2. Solution Planning and Strategy"
echo "3. Implementation and Execution"
echo "4. Testing and Validation"
echo "5. Refinement and Optimization"
echo ""
# Context extraction
echo "🎯 Key Context Elements:"
echo "- Primary objective: [Main goal being pursued]"
echo "- Technology stack: [Languages, frameworks, tools involved]"
echo "- Project scope: [Boundaries and limitations]"
echo "- Stakeholders: [Who is involved or affected]"
echo "- Timeline: [Any deadlines or schedule considerations]"
Work Completed Analysis:
## 📋 Work Completed Summary
### Major Accomplishments:
- [ ] **[Task Category 1]**: [Specific accomplishments and deliverables]
- Sub-task A: [Details of what was completed]
- Sub-task B: [Details of what was completed]
- Key decisions made: [Important choices and rationale]
- [ ] **[Task Category 2]**: [Specific accomplishments and deliverables]
- Sub-task A: [Details of what was completed]
- Sub-task B: [Details of what was completed]
- Key decisions made: [Important choices and rationale]
### Files Created/Modified:
- `[file-path]`: [Purpose and changes made]
- `[file-path]`: [Purpose and changes made]
- `[file-path]`: [Purpose and changes made]
### Key Decisions and Rationale:
1. **[Decision Topic]**: [Decision made]
- Rationale: [Why this choice was made]
- Alternatives considered: [Other options that were discussed]
- Impact: [How this affects the project]
2. **[Decision Topic]**: [Decision made]
- Rationale: [Why this choice was made]
- Alternatives considered: [Other options that were discussed]
- Impact: [How this affects the project]
### Technical Discoveries:
- [Important technical insights or learnings]
- [Configuration details or setup requirements]
- [Performance considerations or optimizations]
- [Security considerations or requirements]
### Quality Assurance Completed:
- [ ] Code reviews performed: [What was reviewed]
- [ ] Testing completed: [Types of tests and coverage]
- [ ] Documentation updated: [What documentation was created/updated]
- [ ] Standards compliance: [Standards followed and validated]
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.
- 6d ago First seen · 343 lines · 0 tokens per session scan A 524754fa5ff6
prompt-continue-thread 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,656 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
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
dreamd-recall
Recall lessons, decisions, and prior context from the .agent/ memory daemon. Use when starting work in a project that has a .agent/ folder, when the user references a past decision, or when you are about to make a choice that has a documented prior.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
common_memory_bank
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read…
context-recorder-system
Context Recorder System (记录员系统) - 模块化索引文件.
memsprout
Cursor rule "memsprout" from memsprout/agents, covering using memsprout, search first, capturing, spaces and topics and files.