resume

A command for continuing an interrupted agent session from its saved project state.

In plain words
What is it for?
Use it to read the saved status and plan, find the next unfinished task, inspect the project state, and run the project's code-quality check.
Why use it?
It restores the active plan and handover information so work can continue without reconstructing the previous session manually.

Command

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 commands/d-oit/rust-2026-template/resume
Clone the repo
git clone --depth 1 https://github.com/d-oit/rust-2026-template
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 213 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00000 $0.00213
Opus 5 $0.00000 $0.00106
Sonnet 5 $0.00000 $0.00043
Haiku 4.5 $0.00000 $0.00021

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

Security

Grade A, and why

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

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.

.opencode/commands/resume.md · 17 lines

What it actually says

Command: resume

Description

Resumes the agent session from the last recorded state to ensure continuity across interruptions.

Execution Protocol

  1. Status Anchor: Read plans/_status.json to identify the active_plan and any handover_ref.
  2. Handover Recovery: If handover_ref points to a file, read it to restore the previous session's "thought process" and specific context.
  3. Plan Alignment: Load the markdown file associated with the active_plan (typically in the plans/ directory).
    • Identify the current phase.
    • Identify the next pending todo item.
  4. World State: Read plans/GOAP_STATE.md to align with the executable truth of the repository.
  5. Validation: Run ./scripts/code-quality.sh check to ensure the workspace is in a healthy state for continuation.

Goal

Restore the agent's mental model to the exact point of the last save or handoff.

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 · 17 lines · 0 tokens per session scan A 3606b4b10919

Subscribe to this mod's changes

resume is a command published in the GitHub repository d-oit/rust-2026-template (10 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 213 tokens. 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.