continue

continue is a skill for Claude Code from ohong/agent-skills. It costs 45 tokens per session (614 once invoked), scanned A, original, MIT.

A mission-resume skill that reads saved plan, learning, and progress files to continue work from the last completed milestone. A milestone is a meaningful checkpoint in a longer task.

In plain words
What is it for?
Use it when continuing a planned task to identify completed steps, the next step, blockers, and the acceptance criteria for the work ahead.
Why use it?
It restores the task's current state after a context reset or new session, reducing the need to reconstruct what was already done.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Part of the mission plugin — 6 skills shipped together

Good fit Use it when continuing a planned task to identify completed steps, the next step, blockers, and the acceptance criteria for the work ahead.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ohong/agent-skills/continue
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.

Any agent
npx skills add ohong/agent-skills --skill continue
Clone the repo
git clone --depth 1 https://github.com/ohong/agent-skills

Made for: Claude Code.

Or install mission, the plugin that ships this one along with the rest of its 6 skills.

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 continue

README.md
[![agentmods](https://agentmods.dev/badge/skills/ohong/agent-skills/continue/github.svg)](https://agentmods.dev/skills/ohong/agent-skills/continue)
Your own site
<a href="https://agentmods.dev/skills/ohong/agent-skills/continue"><img src="https://agentmods.dev/badge/skills/ohong/agent-skills/continue/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for continue

Your own site · 80×15
<a href="https://agentmods.dev/skills/ohong/agent-skills/continue"><img src="https://agentmods.dev/badge/skills/ohong/agent-skills/continue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 614 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.00045 $0.00614
Opus 5.5 $0.00018 $0.00246
Sonnet 5.5 $0.00009 $0.00123
Haiku 4.5 $0.00005 $0.00061

Measured 1mo ago against content hash 48f15e8a5195, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

mission/skills/continue/SKILL.md · 68 lines

How it starts

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

Mission Continue — Forced Reorientation

Context refresh is not a limitation — it's Boyd's reorientation in action.

You are resuming a mission with fresh context. This is the most powerful moment in the OODA cycle: your old context, with its accumulated drift, stale assumptions, and lost-in-the-middle effects, is gone. You start clean. The .mission/ files carry your shared orientation forward.


Reorientation procedure

1. Observe — Read the state from disk

Read these files in order (background first, current task last — recency anchoring):

  1. .mission/plan.md — the full plan (shared intent)
  2. .mission/learnings.md — if it exists, patterns from earlier work (shared experience)
  3. .mission/progress.md — current state (shared situation awareness) — read this last so it's freshest in context

If .mission/plan.md doesn't exist: "No mission plan found. Run /mission:plan <task> first." Stop.

2. Orient — Build your mental model

From the files, identify:

  • Which milestones are completed ([x])
  • Which milestone is next (first [ ] or [>])
  • Any notes about blockers, partial work, or discoveries
  • The acceptance criteria for the next milestone

3. Announce — Confirm orientation

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
MISSION RESUMED
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Completed: {N}/{total} milestones
Resuming:  Milestone {N+1}: {title}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

4. Mismatch check

If progress notes mention partially completed work:

  • Read the relevant source files from disk
  • Run a quick verification — does the current state match what progress.md claims?
  • If there's a mismatch between progress notes and actual file state, trust the FILES. Update progress.md to reflect reality.

5. Execute — Enter the OODA cycle

Follow the execution protocol in ../../references/execution-protocol.md starting from the next incomplete milestone.

The principle

You have fresh context. This is an advantage, not a handicap. You don't carry forward stale assumptions, accumulated drift, or mid-context attention degradation. You start with a clean orientation built from ground truth (the files).

Read the full file on GitHub · 68 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. 1mo ago First seen · 68 lines · 45 tokens per session scan A 48f15e8a5195

Subscribe to this mod's changes

continue is a skill published in the GitHub repository ohong/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 614 once invoked, about $0.0002 per session on Opus 5.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

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

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

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 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

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens