resume

resume is a command for Claude Code from reganomalley/claudia. It costs 25 tokens per session (1,194 once invoked), scanned A, original, MIT.

A session-resume command that reads project notes, Git history, and available context to reconstruct where development work stopped.

In plain words
What is it for?
It is for resuming work in the current project, selecting a registered project, or viewing a dashboard of recent projects and their status.
Why use it?
It reduces the time needed to remember unfinished work when returning to a project or switching between registered projects.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

Part of the claudia plugin — 10 skills, 12 commands, 5 hooks shipped together

Good fit It is for resuming work in the current project, selecting a registered project, or viewing a dashboard of recent projects and their status.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/reganomalley/claudia/resume
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.

Clone the repo
git clone --depth 1 https://github.com/reganomalley/claudia

Made for: Claude Code.

Or install claudia, the plugin that ships this one along with the rest of its 10 skills, 12 commands, 5 hooks.

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 resume

README.md
[![agentmods](https://agentmods.dev/badge/commands/reganomalley/claudia/resume/github.svg)](https://agentmods.dev/commands/reganomalley/claudia/resume)
Your own site
<a href="https://agentmods.dev/commands/reganomalley/claudia/resume"><img src="https://agentmods.dev/badge/commands/reganomalley/claudia/resume/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 resume

Your own site · 80×15
<a href="https://agentmods.dev/commands/reganomalley/claudia/resume"><img src="https://agentmods.dev/badge/commands/reganomalley/claudia/resume.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,194 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.00025 $0.01194
Opus 5 $0.00013 $0.00597
Sonnet 5 $0.00005 $0.00239
Haiku 4.5 $0.00003 $0.00119

Measured 8d ago against content hash fac4930bfe9d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 8d 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.

commands/resume.md · 111 lines

How it starts

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

Claudia: Resume Session

You are Claudia, helping the user pick up where they left off.

Determine Context

First, figure out where the user is:

  1. Check if $ARGUMENTS matches a registered project. Read ~/.claude/claudia-projects.json (the registry). If $ARGUMENTS matches a project name or path, use that project. cd to its path and do single-project resume.

  2. Check if we're at ~ (home directory) with no arguments. If so, show the multi-project dashboard (see below).

  3. Otherwise, do single-project resume for the current directory.


Multi-Project Dashboard (from ~)

Read ~/.claude/claudia-projects.json. If it doesn't exist or has no projects:

"No projects registered yet. Try /claudia:start to create one, or cd into a project and I'll pick up from there."

If projects exist, show up to 10 sorted by last_active (most recent first):

Your projects:

1. {name} ({path})
   Stack: {stack summary} | Last active: {relative time}
   Status: {git status summary}

2. {name} ({path})
   Stack: {stack summary} | Last active: {relative time}
   Status: {git status summary}

For each project:

  • Read its per-project file from ~/.claude/claudia-projects/{key}.json for stack info
  • Run git -C {path} log --oneline -1 for last commit
  • Run git -C {path} status --short for uncommitted changes
  • Summarize status: "clean", "uncommitted changes in N files", "N commits ahead", etc.
  • Format last_active as relative time: "today", "yesterday", "3 days ago", etc.

End with: "Which project do you want to pick up? Say its name or number."


Single-Project Resume

  1. Gather context from all sources. Check these in order, reading whatever exists:

    Project context (primary):

    • Read project-scoped context: check ~/.claude/claudia-projects.json for a key matching this directory, then read ~/.claude/claudia-projects/{key}.json
    • Fall back to ~/.claude/claudia-context.json if no project-scoped file exists

    Session notes:

    • If the user provided a path via $ARGUMENTS (and it wasn't a project name), read that file
    • Look for claudia-session-*.md files in the current working directory (pick the most recent)
    • Look for session-notes*.md, SESSION.md, or HANDOFF.md in the current directory
    • Check ~/.claude/projects/ for any recent session transcripts

Read the full file on GitHub · 111 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. 8d ago First seen · 111 lines · 25 tokens per session scan A fac4930bfe9d

Subscribe to this mod's changes

resume is a command published in the GitHub repository reganomalley/claudia (4 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 1,194 once invoked, about $0.0001 per session on Opus 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.