continue

A session-resume tool that loads a handoff file containing notes about unfinished development work.

In plain words
What is it for?
It finds the relevant handoff, reads linked specifications and review notes, summarizes the current task and open questions, and asks whether to continue.
Why use it?
It reduces the need to reconstruct project context manually after starting a new session.

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/dixus/claudeframework/continue
Any agent
npx skills add dixus/claudeframework --skill continue
Clone the repo
git clone --depth 1 https://github.com/dixus/claudeframework

Made for: Claude Code, Codex.

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 296 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.00028 $0.00296
Opus 5 $0.00014 $0.00148
Sonnet 5 $0.00006 $0.00059
Haiku 4.5 $0.00003 $0.00030

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

Security

Grade B, and why

continue 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.

- Otherwise: find the most recently modified `.md` file in `.claude/handoffs/`
.claude/skills/continue/SKILL.md · 27 lines

What it actually says

Restore context from a handoff file and prepare to resume work.

$ARGUMENTS is optional — pass a filename or label to load a specific handoff. Without arguments, loads the most recently modified file in .claude/handoffs/.

Steps

  1. Find the handoff file:
    • If $ARGUMENTS provided: look for .claude/handoffs/<ARGUMENTS>.md or the closest match by name
    • Otherwise: find the most recently modified .md file in .claude/handoffs/
  2. Read the handoff file in full
  3. Read the referenced spec file (if listed under "Active files")
  4. Read the referenced review file (if listed under "Active files")
  5. Briefly read the listed key source files — enough to understand current state, not full implementation detail
  6. Report a summary to the user:
    • Current task (one sentence)
    • Pipeline position
    • Open questions (if any)
    • Proposed next step (verbatim from handoff)
  7. Ask: "Ready to continue with [next step]?" — wait for confirmation before doing anything
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 · 27 lines · 28 tokens per session scan B 7c21388eb3a4

Subscribe to this mod's changes

continue is a skill published in the GitHub repository dixus/claudeframework (10 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 296 once invoked, about $0.0001 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens