prompt-continue-thread

prompt-continue-thread is a cursor rule for Cursor from oakensoul/nextjs-cursor-prompts. It costs 0 tokens per session (2,656 once invoked), scanned A, original, MIT.

A prompt for carrying work from one conversation thread into another by summarizing progress, decisions, project state, and unfinished tasks. A conversation thread is one continuous chat.

In plain words
What is it for?
Use it to create a handoff summary containing completed work, open tasks, key decisions, and a starting point for the next conversation.
Why use it?
It reduces the risk of losing important context when a chat becomes too long or work must continue in a new thread.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

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.

agentmods
npx agentmods add rules/oakensoul/nextjs-cursor-prompts/prompt-continue-thread
Clone the repo
git clone --depth 1 https://github.com/oakensoul/nextjs-cursor-prompts

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.

agentmods badge for prompt-continue-thread

README.md
[![agentmods](https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/prompt-continue-thread.svg)](https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/prompt-continue-thread)
Your own site
<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>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,656 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce 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

Measured 6d ago against content hash 524754fa5ff6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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.

.cursor/prompts/prompt-engineering/prompt-continue-thread.mdc · 343 lines

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:

  1. SUMMARIZE accomplished tasks and deliverables from current thread
  2. IDENTIFY unfinished work and next steps requiring continuation
  3. EXTRACT key decisions and important context for new thread
  4. DOCUMENT project state with actionable handoff information
  5. 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]

Read the full file on GitHub · 343 lines

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.

  1. 6d ago First seen · 343 lines · 0 tokens per session scan A 524754fa5ff6

Subscribe to this mod's changes

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.