A session handoff record that stores what was completed, what should happen next, and any blockers. A blocker is an unresolved problem that prevents progress.

Use it at the end of a work session or midway through a task to save progress, plans, decisions, file names, and unresolved issues.

It prevents work from being lost when a coding session ends or changes hands. Specific next steps let a new session resume without relying on memory.

checkpoint — Cursor rule for Cursor by Jkudjo/oh-my-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.

Clone the repo

git clone --depth 1 https://github.com/Jkudjo/oh-my-cursor

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/jkudjo/oh-my-cursor/checkpoint/github.svg)](https://agentmods.dev/rules/jkudjo/oh-my-cursor/checkpoint)

Your own site

<a href="https://agentmods.dev/rules/jkudjo/oh-my-cursor/checkpoint"><img src="https://agentmods.dev/badge/rules/jkudjo/oh-my-cursor/checkpoint/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/jkudjo/oh-my-cursor/checkpoint"><img src="https://agentmods.dev/badge/rules/jkudjo/oh-my-cursor/checkpoint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 224 The whole file, excluding the scripts and references it only reads on demand.

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.00013	$0.00224
Opus 5.5	$0.00005	$0.00090
Sonnet 5.5	$0.00003	$0.00045
Haiku 4.5	$0.00001	$0.00022

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

Security

Grade A, and why

checkpoint 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 1mo 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.

rules/checkpoint.mdc · 33 lines

What it actually says

@checkpoint

Trigger: At the end of a working session, or when you want to save progress mid-session.

Protocol

Summarize what was accomplished in this session (specific, not vague).
Write exact next steps — specific enough that a fresh session can resume without context.
Note any blockers or unresolved decisions.
Call save_checkpoint with summary, next_steps, blockers.
Also call save_artifact type=logs, slug=session-{date}, with a full session log.

Output

Checkpoint saved.

Summary: {what was done}
Next session: {exact next steps}
Blockers: {any blockers, or "none"}

Rules

Be specific in next_steps — "implement step 3 of plan-XXXXX" not "continue the plan"
Reference plan IDs, task IDs, and file names in next_steps so the next session can resume precisely

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.

1mo ago First seen · 33 lines · 13 tokens per session scan A d8a42785edea

Subscribe to this mod's changes

checkpoint is a cursor rule published in the GitHub repository Jkudjo/oh-my-cursor (1 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 224 once invoked, about $0.0001 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.

Memory and context agent ai-workflow codex cursor cursor-ai cursor-rules

100-memory-system

Comprehensive Memory System architecture for autonomous Cursor operation.

aiurda/cursor10x · 1,232 tokens

memory-protocol

A protocol for storing and retrieving project memories from files, using a command-line memory tool. It records decisions, preferences, dates, tasks, and other useful history for later conversations.

nongjun/feishu-cursor-claw · 1,070 tokens

create-rule-agent

This rule is responsible for creating and updating Cursor rules. Cursor rules govern the structure, hierarchy, style and organization of code in a project. This rule should be invoked in Agent mode when: 1. a user wants to create a new cursor rule, 2. a user wants to update or change an existing rule, 3. user wants…

usrrname/cursorrules · 3,429 tokens

checkpoint