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 skills/betmoar/cc-reload-plugin/maintaining-session-continuitynpx skills add betmoar/cc-reload-plugin --skill maintaining-session-continuitygit clone --depth 1 https://github.com/betmoar/cc-reload-pluginWrote 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/skills/betmoar/cc-reload-plugin/maintaining-session-continuity)<a href="https://agentmods.dev/skills/betmoar/cc-reload-plugin/maintaining-session-continuity"><img src="https://agentmods.dev/badge/skills/betmoar/cc-reload-plugin/maintaining-session-continuity.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.00110 | $0.00985 |
| Opus 5 | $0.00055 | $0.00492 |
| Sonnet 5 | $0.00022 | $0.00197 |
| Haiku 4.5 | $0.00011 | $0.00098 |
Grade A, and why
maintaining-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 today.
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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintaining session continuity
cc-reload preserves an ordinary session's working thread across a context reset. It does not drive
work (that's a loop — use cc-repete); it snapshots the thread to .reload/session.md before a
reset and hands it back after.
The cycle: budget → snapshot → arm → rehydrate
Reset before rot, and long before auto-compaction — stay well under the window, never let auto-compact fire.
- Budget — the Stop hook watches occupancy; crossing
context_budget_pct(default 45) escalates percontext_budget_mode: notify (default) nudges in one status line, never blocks, re-nudges only every ~10 further points; snapshot forces the digest turn and arms./reload-budget <pct>tunes it,/reload-budget notify|snapshotswitches mode. - Snapshot — a fresh digest is written (budget prompts it;
/snapshotforces one). - Arm —
.reload/pendingmeans "rehydrate on the next reset". Only armed resets rehydrate, so a deliberate/clearmeant to drop context isn't undone. - Rehydrate — SessionStart injects the digest and consumes the marker. Automatic;
/reloaddoes it on demand.
Judgment that isn't obvious from the mechanism
Lower the budget than you think. Occupancy is a % of the main session model's window (1M on
current large-context models). Effective context — where reasoning stays sharp — degrades well
before the raw window fills, so 45% of 1M is generous: prefer ~30 or lower for reasoning-heavy or
context-sensitive work. Non-Claude models routed through the cc-proxy plugin (e.g. glm-4.5 at
128K, glm-4.6/glm-5 at 200K) have real windows far smaller than 1M. SessionStart learns this
live from cc-proxy itself (one loopback-only call to its /v1/models, fired once per session) when
the proxy is reachable; model_window()'s curated table is the offline fallback. An id neither the
proxy nor the table knows still falls back to the optimistic 1M assumption, so pin context_window
explicitly if you're running a small-window proxy model and the proxy might not be up at session
start.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +1 lines 72881ea96794
- 5d ago First seen · 69 lines · 110 tokens per session scan A 471a0e8d7ada
maintaining-session-continuity is a skill published in the GitHub repository betmoar/cc-reload-plugin (1 stars, last pushed yesterday), licensed MIT. It adds 110 tokens to every session and 985 once invoked, about $0.0006 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 skills, from other repositories
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
recall
Must be used at the start of any non-trivial task involving code changes, debugging, repo exploration, file inspection, or environment/tooling investigation to surface stored guidance before analysis or tool use.
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.
knowledge-priming-refiner
Facilitate a structured conversation to create a project-specific knowledge base document. Produces a knowledge-base.md that primes AI with the project's tech stack, architecture, trusted sources, and project structure. Use when the user says 'set up knowledge base', 'prime the project', 'onboard AI', 'create…
alive-people
Weekly -- cross-reference people mentions, nudge stale contacts.
alive-inbox
Scan 03Inbox/ for unrouted files, present routing suggestions.