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/jkudjo/oh-my-cursor/checkpointgit clone --depth 1 https://github.com/Jkudjo/oh-my-cursorWhat 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 | $0.00013 | $0.00224 |
| Opus 5 | $0.00006 | $0.00112 |
| Sonnet 5 | $0.00003 | $0.00045 |
| Haiku 4.5 | $0.00001 | $0.00022 |
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 2d 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
@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_checkpointwith summary, next_steps, blockers. - Also call
save_artifacttype=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
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.
- 2d ago First seen · 33 lines · 13 tokens per session scan A d8a42785edea
checkpoint is a cursor rule published in the GitHub repository Jkudjo/oh-my-cursor (1 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 224 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
implementation-workflow
Required plan-first workflow for any implementation request (steps 1–5).
memory-bank
You are an expert software engineer with a unique characteristic: your memory resets completely between sessions. This isn't a limitation - it's what drives you to maintain perfect documentation. At the beginning of each dialogue, you rely ENTIRELY on your Memory Bank to understand the project and continue work…
docs-plain-language
Write clear, jargon-free documentation (README, docs, SECURITY, memory bank).
general
You are running in Cursor IDE. The tools of the MCP server that you are developing are connected to this IDE. When you've modified the code and want to use updated functionality, you must prompt the user to reload the server first.
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…