Agent skill

Agent Session Resume

by hacktivist123 in hacktivist123/agent-session-resume

A skill your agent uses when continuing, resuming, locating, reading, inspecting, auditing, or reviewing a previous AI coding-agent session, handoff transcript, chat log, exported conversation…

MITAuto-check passedAgent Workflows

Install Agent Session Resume

skills CLI
$ npx skills add hacktivist123/agent-session-resume --skill agent-session-resume -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hacktivist123/agent-session-resume agent-session-resume --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hacktivist123/agent-session-resume.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/agent-session-resume .claude/skills/agent-session-resume && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
agent-session-resume
GitHub stars
243
Token cost
~1.7k tokens
SKILL.md length
692 words
Files
14 (incl. scripts, references)
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when continuing, resuming, locating, reading, inspecting, auditing, or reviewing a previous AI coding-agent session, handoff transcript, chat log, exported conversation…

  • Works in 9 steps: Run a provenance self-check. → Identify the source. If the user names a… → Locate the transcript or best… → …
  • Reviewing a previous AI coding-agent session
  • SKILL.md covers Purpose, Core Workflow, Resume Modes and Platform References, plus 2 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Agent Session Resume is an agent skill from hacktivist123/agent-session-resume. Use when continuing, resuming, locating, reading, inspecting, auditing, or reviewing a previous AI coding-agent session, handoff transcript, chat log, exported conversation, saved artifact set, or session summary, on any platform (Claude Code, Codex, Cursor, Antigravity, OpenCode) or across several platforms in one ask, such as reviewing threads across Claude and Codex.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 16 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/antigravity.md` and `references/claude-code.md`).

It sits in Agent Workflows, covering Session handoff. The repository describes itself as: Cross-agent session resume skill for Claude Code, Codex, Antigravity, and OpenCode. The licence is MIT.

When your agent uses it

  • Reviewing a previous AI coding-agent session
  • Handoff transcript
  • Exported conversation
  • Saved artifact set

Example prompts

  • “/agent-session-resume”

Requirements

  • Python 3

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Run a provenance self-check.
  2. Identify the source. If the user names a platform, read the matching file in references/; if the ask spans platforms, read…
  3. Locate the transcript or best substitute. Prefer full transcripts over summaries, workspace-local session data over global history, and…
  4. Read the full available session record before acting. For large transcripts, inventory files, event types, and timestamps first, then read…
  5. Record loaded-skill provenance in the report: path and source/version marker, or unknown, never a guess. Details…
  6. Reconstruct context. Summarize the goal, decisions, constraints, and preferences; identify completed work, changed files, commands and…
  7. Extract tasks. Capture explicit TODOs, plans, and open questions; infer implicit tasks from failing tests, unfinished edits, and "next…
  8. Validate against the workspace. Inspect git status before editing and mention it in the checkpoint; read files the prior session touched…
  9. Continue from the first unfinished step. Do not repeat completed work; follow the established approach and style unless clearly broken…

What it can do on your machine

Read from SKILL.md and the folder at commit 76b0256. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 4 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Agent Session Resume loads about 1.7k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 98 tokens; SKILL.md has 692 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~98
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~17k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from hacktivist123/agent-session-resume at commit 76b0256, republished under its MIT licence (© hacktivist123). 692 words, ~1,652 tokens.

Download SKILL.mdSave it as .claude/skills/agent-session-resume/SKILL.md (or your agent's skills folder). This skill also uses 13 other files; get the full folder from GitHub.
name
agent-session-resume
description
Use when continuing, resuming, locating, reading, inspecting, auditing, or reviewing a previous AI coding-agent session, handoff transcript, chat log, exported conversation, saved artifact set, or session summary, on any platform (Claude Code, Codex, Cursor, Antigravity, OpenCode) or across several platforms in one ask, such as reviewing threads across Claude and Codex.

Agent Session Resume

Purpose

Resume or audit prior coding-agent work with continuity. Reconstruct what happened before acting, then continue from the real stopping point.

Core Workflow

  1. Run a provenance self-check.

    • Run python3 skills/agent-session-resume/scripts/skill-provenance.py when available.
    • Otherwise compare the loaded SKILL.md path and size against the known install paths under $HOME/.claude and ${CODEX_HOME:-$HOME/.codex}.
    • Report staleness on the Loaded skill line of the resume report. Details: references/evidence-and-provenance.md.
  2. Identify the source. If the user names a platform, read the matching file in references/; if the ask spans platforms, read references/cross-platform.md. Otherwise inspect the workspace for session folders, exports, summaries, and artifacts. When a session title is given, prefer exact or fuzzy title matches over recency.

  3. Locate the transcript or best substitute. Prefer full transcripts over summaries, workspace-local session data over global history, and explicit user-provided paths over discovered paths.

  4. Read the full available session record before acting. For large transcripts, inventory files, event types, and timestamps first, then read the evidence-bearing slices until the record is accounted for. Full coverage means no relevant evidence skipped; bounded searches and slices are fine for giant records, but say so and name the file/event. Do not edit files or repeat prior work before this pass is complete.

  5. Record loaded-skill provenance in the report: path and source/version marker, or unknown, never a guess. Details: references/evidence-and-provenance.md.

  6. Reconstruct context. Summarize the goal, decisions, constraints, and preferences; identify completed work, changed files, commands and tests run; pin the exact stopping point. Every work-state claim carries an evidence ref (src/file.ts:L20-L35, transcript lines, command output, or explicit "not checked yet"). Prior resume reports, summaries, and handoffs are claims, not primary evidence: re-verify against transcripts, files, git state, or command output, or label them unverified. Preserve explicit user deferrals ("skip", "park", "not now", "hold") with evidence, scope, and reopen condition.

  7. Extract tasks. Capture explicit TODOs, plans, and open questions; infer implicit tasks from failing tests, unfinished edits, and "next step" language. Keep specific unfinished tasks specific. Track deferred work separately from NOT DONE. Classify: DONE (completed and verified, or no longer needed), PARTIALLY DONE (started but missing implementation, tests, review, commit, push, or confirmation), NOT DONE (not started or only discussed).

  8. Validate against the workspace. Inspect git status before editing and mention it in the checkpoint; read files the prior session touched. Preserve unrelated user changes in a dirty worktree; use a separate worktree or ask before colliding work. If transcript claims conflict with current files, trust current files and report the mismatch.

  9. Continue from the first unfinished step. Do not repeat completed work; follow the established approach and style unless clearly broken. Ask the user only when blocked by missing information or an unsafe choice.

Show full SKILL.md (240 more words)Show less

Resume Modes

Decide from the user's prompt how far to go after the checkpoint:

  • Report-only: the ask is what happened, done versus pending, or to check/audit/review a prior session without edits. Stop after the resume report and clear next action.
  • Continue-edit: the ask is to continue, fix, implement, open a PR, or run tests. Report first, then continue from the first unfinished safe step.
  • Quick resume: status report or task breakdown. Prefer a compact source inventory, task classification, and next action.
  • Deep resume: implementation continues, the source is ambiguous, or files may have drifted. Read the full record and current git state, then continue.

Platform References

  • Claude Code: references/claude-code.md
  • Codex: references/codex.md
  • Cursor: references/cursor.md
  • Antigravity: references/antigravity.md
  • OpenCode: references/opencode.md
  • GitHub Copilot: references/github-copilot.md
  • Cross-platform / multi-agent asks: references/cross-platform.md

Required Response Shape

Before continuing execution, report:

markdown
## Brief context summary

- Goal: <prior session goal>
- Loaded skill: path=<loaded SKILL.md path or "unknown">; source/version=<version marker or "unknown">
- Source reviewed: <transcript/export/artifact refs>
- Current workspace check: <git status summary and touched-file refs, or why not checked>
- Transcript/current repo mismatches: <none found | claim, transcript ref, current-repo ref, action>
- User deferrals: <none found | deferred scope, user wording, evidence ref, reopen condition>
- Stopping point: <last command, edit, failure, or user pause instruction with evidence>

## Task status breakdown

- DONE: <task> - evidence: <implementation refs>; verification: <test/tool refs or "not recorded">.
- PARTIALLY DONE: <task> - evidence: <started-work refs>; missing: <remaining gap refs>.
- NOT DONE: <task> - evidence: <TODO, failing test, absent artifact, or transcript gap refs>.

## Clear next action

- Next: <first unfinished step to take now>
- Blocked: <no | yes - reason and evidence>

Then continue immediately unless blocked. Evidence rules and the static idempotency contract: references/evidence-and-provenance.md.

Guardrails

  • Never assume the newest file is the right transcript when the user supplied a title or path.
  • Never summarize from filenames alone or treat a compact summary as equivalent to an available full transcript.
  • Never reset, revert, or discard existing changes unless the user explicitly asks.
  • Never mark a task DONE or PARTIALLY DONE from a plan alone; status requires evidence of completion or started work.
  • Never omit transcript/current-repo mismatches when the transcript and checked files disagree.
  • Never unpark deferred scope from a vague "proceed" or "continue"; confirm the user wants that parked work reopened.

© hacktivist123, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 13 other files (scripts, references) in skills/agent-session-resume of hacktivist123/agent-session-resume.

  • SKILL.md
  • agents/openai.yaml
  • references/antigravity.md
  • references/claude-code.md
  • references/codex.md
  • references/cross-platform.md
  • references/cursor.md
  • references/evidence-and-provenance.md
  • references/github-copilot.md
  • references/opencode.md
  • scripts/session-candidates.py
  • scripts/session-digest.py
  • scripts/session-events.py
  • scripts/skill-provenance.py

Open the folder on GitHubat commit 76b0256

Compare with similar skills

Agent Session Resume next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Agent Session Resume compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agent Session Resume this skillhacktivist123/agent-session-resume243—~1.7kAutomated safety check: PassMIT
Orca CLIstablyai/orca87k2 repos~593Automated safety check: PassMIT
Beads Task Memorygastownhall/beads28k—~1.2kAutomated safety check: PassMIT
Session History Searchslopus/happy24k—~3.1kAutomated safety check: PassMIT
Paseo Agent Handoffgetpaseo/paseo20k1 repos~606Automated safety check: PassCustom licence
Memori Long-Term MemoryMemoriLabs/Memori17k—~2kAutomated safety check: NotesCustom licence

Similar skills

  • Orca CLI

    stablyai/orca

    Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…

    87k GitHub starsUsed in 2 repos~593 tokens
    Agent WorkflowsAuto-check passed
  • Beads Task Memory

    gastownhall/beads

    Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.

    28k GitHub stars~1.2k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.

    24k GitHub stars~3.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Paseo Agent Handoff

    getpaseo/paseo

    Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.

    20k GitHub starsUsed in 1 repo~606 tokens
    Agent WorkflowsAuto-check passed
  • Memori Long-Term Memory

    MemoriLabs/Memori

    Connects Claude Code to Memori Cloud for long-term memory, recalling stored context before substantive replies and saving new context afterward.

    17k GitHub stars~2k tokensUpdated 5 days ago
    Agent WorkflowsAuto-check: notes
  • Beads

    liwp/again

    A skill your agent uses when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory.

    118 GitHub starsUsed in 6 repos~537 tokens
    Agent WorkflowsAuto-check passed

Categories

Questions about Agent Session Resume

What does Agent Session Resume do?

A skill your agent uses when continuing, resuming, locating, reading, inspecting, auditing, or reviewing a previous AI coding-agent session, handoff transcript, chat log, exported conversation…. Agent Session Resume is an agent skill from hacktivist123/agent-session-resume. Use when continuing, resuming, locating, reading, inspecting, auditing, or reviewing a previous AI coding-agent session, handoff transcript, chat log, exported conversation, saved artifact set, or session summary, on any platform (Claude Code, Codex, Cursor, Antigravity, OpenCode) or across several platforms in one ask, such as reviewing threads across Claude and Codex.

When should I use Agent Session Resume?

Agent Session Resume fits situations like: reviewing a previous AI coding-agent session; handoff transcript; exported conversation; saved artifact set.

How do I install Agent Session Resume in Claude Code?

Run `npx skills add hacktivist123/agent-session-resume --skill agent-session-resume -a claude-code`. Or copy the skill folder (skills/agent-session-resume in hacktivist123/agent-session-resume) into .claude/skills/agent-session-resume in your project. Claude Code loads it when a task matches its description.

How do I install Agent Session Resume in Codex?

Run `npx skills add hacktivist123/agent-session-resume --skill agent-session-resume -a codex`. Or copy the skill folder (skills/agent-session-resume in hacktivist123/agent-session-resume) into .agents/skills/agent-session-resume in your project. Codex loads it when a task matches its description.

Can I use Agent Session Resume in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hacktivist123/agent-session-resume --skill agent-session-resume -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-session-resume, .gemini/skills/agent-session-resume, .github/skills/agent-session-resume and .opencode/skills/agent-session-resume in your project.

What does Agent Session Resume need to run?

Going by SKILL.md and its folder, Agent Session Resume needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Agent Session Resume access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Agent Session Resume safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Agent Session Resume use?

Agent Session Resume is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Agent Session Resume use?

About 1.7k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 15k tokens, read only when the agent opens those files.

What are the alternatives to Agent Session Resume?

Skills that share tags, products or a category with Agent Session Resume: Orca CLI (stablyai/orca, 87k stars), Beads Task Memory (gastownhall/beads, 28k stars), Session History Search (slopus/happy, 24k stars) and Paseo Agent Handoff (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agent Session Resume?

hacktivist123 (a GitHub user) maintains it in hacktivist123/agent-session-resume, which has 243 GitHub stars. The repository was last updated on June 30, 2026.

Source: hacktivist123/agent-session-resume on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.