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/igorganapolsky/thumbgate/session-continuitygit clone --depth 1 https://github.com/IgorGanapolsky/ThumbGateWhat 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.00019 | $0.00188 |
| Opus 5 | $0.00010 | $0.00094 |
| Sonnet 5 | $0.00004 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
session-continuity 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 3d 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
Session Continuity
Maintain context across coding sessions using the ThumbGate memory system.
Session start
- Call the
recallMCP tool to retrieve:- Recent prevention rules relevant to the current project
- Past failure patterns and corrective actions
- Active context packs from previous sessions
- Summarize recalled context before starting work.
Session end
- Capture any new feedback from the session using
capture_feedback. - Note any unfinished work or pending decisions as context for the next session.
- If new failure patterns emerged, flag them for potential prevention rule promotion.
Between sessions
- Prevention rules persist automatically via the MCP server.
- Lessons promoted during the session are available in future recalls.
- Context packs expire based on configured retention policies.
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.
- 3d ago First seen · 29 lines · 19 tokens per session scan A b4ebc2cd07df
session-continuity is a cursor rule published in the GitHub repository IgorGanapolsky/ThumbGate (26 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 188 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-30.
Other cursor rules, from other repositories
cursor
Before telling the user a task is done, you MUST.
cursorrules
This project uses Phantom Secrets to protect API keys from AI leaks.
selectools-development
Selectools development conventions, testing requirements, and release process.
selectools-providers
Rules for working with LLM provider adapters in selectools.
titanclip-monorepo
TitanClip pnpm monorepo layout, scripts, and scoping.
titanclip-cursor-adapter
Cursor local adapter — CLI integration and skills sync.