resume

A procedure for continuing unfinished coding work in a new session by checking the current files, Git repository, GitHub data, plan, and task list. Git records code changes and branches; GitHub hosts shared repositories and pull requests.

In plain words
What is it for?
Use it when returning to an interrupted task, checking whether changes were committed or merged, and confirming which planned items still need work.
Why use it?
It prevents repeating work that is already finished or relying on notes that no longer match the repository.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/dryvist/claude-code-plugins/resume
Any agent
npx skills add dryvist/claude-code-plugins --skill resume
Clone the repo
git clone --depth 1 https://github.com/dryvist/claude-code-plugins

Made for: Claude Code, Codex.

Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,235 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
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 $0.00098 $0.01235
Opus 5 $0.00049 $0.00617
Sonnet 5 $0.00020 $0.00247
Haiku 4.5 $0.00010 $0.00123

Measured 2d ago against content hash 294a29ed6aca, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

resume scanned grade B with 1 finding 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

if not, find the most recent under `<HOME>/.claude/plans/`.
ai-cli-harness-better-practices/skills/resume/SKILL.md · 110 lines

How it starts

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

Resume

Continue unfinished work in a session that has no memory of how it got here. The core rule: trust live state, never prose. A resume prompt, a plan file, or a prior summary describes what was true. Before acting, verify what is true.

This exists because resuming cold is common and easy to get wrong: the failure mode is redoing work that already shipped, or acting on a claim that has since gone stale.

State warning: everything below drifts. A PR called "open" in the prompt may be merged; a plan item marked [ ] may be done. Re-derive all of it now.

Step 1: Locate the work

  • Read the plan file. The resume prompt should name it (<HOME>/.claude/plans/<slug>.md); if not, find the most recent under <HOME>/.claude/plans/.
  • TaskList — the pending/in-progress items.
  • The directory the work lives in — the prompt's cd block. Only if that is missing and git rev-parse --is-inside-work-tree succeeds, widen the search with git worktree list.

Step 2: Re-derive live state (never trust the prompt's claims)

For every claim the prompt or plan makes, run the check that confirms it. Pick the cheapest evidence source that can actually falsify the claim:

Evidence source Confirms
The file itself "file Y still needs Z" — read it; the change may already be there
Test or build output "it works" / "it's broken" — run it
TaskList and the plan checkbox a claim, never proof — treat as the thing to verify, not the verification
Filesystem "the artifact was generated", "the config exists"
Version control (repository only) "branch X is pushed", "PR #N is open", "already merged"

The version-control row is gated:

git rev-parse --is-inside-work-tree >/dev/null 2>&1

When it succeeds, add gh pr view <N> --json state,mergedAt (a PR called open may be merged), git status -sb, and gh pr list --state merged to catch work already shipped.

To find commits not yet on the default branch, run this as one block — the resolution and its use must share a shell (see ARCHITECTURE.md):

Read the full file on GitHub · 110 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. 2d ago First seen · 110 lines · 98 tokens per session scan B 294a29ed6aca

Subscribe to this mod's changes

resume is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 98 tokens to every session and 1,235 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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

rspec

This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing spec.rb files, working in spec/ directory, planning implementation phases that…

hoblin/claude-ruby-marketplace · 125 tokens

activerecord

This skill should be used when the user asks to "write a migration", "add a column", "add column to table", "create an index", "add a foreign key", "set up associations", "fix N+1 queries", "optimize queries", "add validations", "create callbacks", "use eager loading", or mentions ActiveRecord, belongsto, hasmany…

hoblin/claude-ruby-marketplace · 180 tokens

dragonruby

This skill should be used when the user asks to "create a game", "make a game", "game development", "dragonruby", "drgtk", "game loop", "tick method", "sprite rendering", "game state", or mentions args.outputs, args.state, args.inputs, coordinate system, collision detection, animation frames, or scene management.…

hoblin/claude-ruby-marketplace · 100 tokens

draper-decorators

This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing…

hoblin/claude-ruby-marketplace · 131 tokens

mcp-server

This skill should be used when the user asks to "create an MCP server", "build MCP tools", "define MCP prompts", "register MCP resources", "implement Model Context Protocol", or mentions the mcp gem, MCP::Server, MCP::Tool, JSON-RPC transport, stdio transport, or streamable HTTP transport. Should also be used when…

hoblin/claude-ruby-marketplace · 98 tokens

ratatui-ruby

This skill should be used when the user asks to "create a TUI", "terminal interface", "terminal UI", "ratatui", "ratatui-ruby", "inline viewport", "full-screen terminal app", "terminal widgets", "tui.draw", "tui.pollevent", or mentions RatatuiRuby.run, managed loop, terminal rendering, Tea MVU, or building CLI…

hoblin/claude-ruby-marketplace · 119 tokens