resume-session

resume-session is a skill for Claude Code, Codex from albatrossflyon-coder/claude-token-operator-kit. It costs 26 tokens per session (1,329 once invoked), scanned A, original, MIT.

A session-resume command that loads the latest saved work from Claude session files. It restores context after starting a new session or continuing work from another day.

In plain words
What is it for?
Use it to continue a saved session, resume work after context limits, or load a specific session file by date or path.
Why use it?
It removes the need to manually reconstruct what was being done and where the previous session stopped.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/you/.claude/session-data/2024-01-15-abc123de-session.tmp.

Good fit Use it to continue a saved session, resume work after context limits, or load a specific session file by date or path.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

Made for: Claude Code, Codex.

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 resume-session

README.md
[![agentmods](https://agentmods.dev/badge/skills/albatrossflyon-coder/claude-token-operator-kit/resume-session.svg)](https://agentmods.dev/skills/albatrossflyon-coder/claude-token-operator-kit/resume-session)
Your own site
<a href="https://agentmods.dev/skills/albatrossflyon-coder/claude-token-operator-kit/resume-session"><img src="https://agentmods.dev/badge/skills/albatrossflyon-coder/claude-token-operator-kit/resume-session.svg" alt="Measured on agentmods" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,329 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.01329
Opus 5 $0.00013 $0.00665
Sonnet 5 $0.00005 $0.00266
Haiku 4.5 $0.00003 $0.00133

Measured 7d ago against content hash 18fe8fba6aa2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

resume-session 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 7d 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.

skills/resume-session/SKILL.md · 157 lines

How it starts

The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Resume Session Command

Load the last saved session state and orient fully before doing any work. This command is the counterpart to /save-session.

When to Use

  • Starting a new session to continue work from a previous day
  • After starting a fresh session due to context limits
  • When handing off a session file from another source (just provide the file path)
  • Any time you have a session file and want Claude to fully absorb it before proceeding

Usage

/resume-session                                                      # loads most recent file in ~/.claude/session-data/
/resume-session 2024-01-15                                           # loads most recent session for that date
/resume-session ~/.claude/session-data/2024-01-15-abc123de-session.tmp  # loads a current short-id session file
/resume-session ~/.claude/sessions/2024-01-15-session.tmp               # loads a specific legacy-format file

Process

Step 1: Find the session file

If no argument provided:

  1. Check ~/.claude/session-data/
  2. Pick the most recently modified *-session.tmp file
  3. If the folder does not exist or has no matching files, tell the user:
    No session files found in ~/.claude/session-data/
    Run /save-session at the end of a session to create one.
    
    Then stop.

If an argument is provided:

  • If it looks like a date (YYYY-MM-DD), search ~/.claude/session-data/ first, then the legacy ~/.claude/sessions/, for files matching YYYY-MM-DD-session.tmp (legacy format) or YYYY-MM-DD-<shortid>-session.tmp (current format) and load the most recently modified variant for that date
  • If it looks like a file path, read that file directly
  • If not found, report clearly and stop

Step 2: Read the entire session file

Read the complete file. Do not summarize yet.

Step 3: Confirm understanding

Respond with a structured briefing in this exact format:

SESSION LOADED: [actual resolved path to the file]
════════════════════════════════════════════════

PROJECT: [project name / topic from file]

WHAT WE'RE BUILDING:
[2-3 sentence summary in your own words]

CURRENT STATE:
PASS: Working: [count] items confirmed
 In Progress: [list files that are in progress]
 Not Started: [list planned but untouched]

WHAT NOT TO RETRY:
[list every failed approach with its reason: this is critical]

OPEN QUESTIONS / BLOCKERS:
[list any blockers or unanswered questions]

NEXT STEP:
[exact next step if defined in the file]
[if not defined: "No next step defined: recommend reviewing 'What Has NOT Been Tried Yet' together before starting"]

════════════════════════════════════════════════
Ready to continue. What would you like to do?

Read the full file on GitHub · 157 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. 7d ago First seen · 157 lines · 26 tokens per session scan A 18fe8fba6aa2

Subscribe to this mod's changes

resume-session is a skill published in the GitHub repository albatrossflyon-coder/claude-token-operator-kit (5 stars, last pushed 18d ago), licensed MIT. It adds 26 tokens to every session and 1,329 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.

Related

Other skills, from other repositories

media-ingest

Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.

garrytan/gbrain · 52 tokens

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

memory

Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.

opensquilla/opensquilla · 44 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens

establishing-project-context

Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.

GanyuanRan/Aegis · 45 tokens