resume

resume is a command for Claude Code from lucasrosati/claude-code-memory-setup. It costs 0 tokens per session (795 once invoked), scanned A, original, MIT.

A command for loading context from earlier sessions using project-specific files in a vault. It finds the current project and reads its saved logs and general rules.

In plain words
What is it for?
Use it when starting or resuming work to load previous session logs, project memory, and applicable vault instructions.
Why use it?
It helps continue work without reconstructing decisions and conventions from scratch. It also handles projects that do not yet have their own vault folder.

Command for Claude Code

Written for Claude Code: SessionEnd hook event. Also seen: mentions CLAUDE.md.

Good fit Use it when starting or resuming work to load previous session logs, project memory, and applicable vault instructions.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/lucasrosati/claude-code-memory-setup/resume
About the project

Claude Code Memory Setup is a workflow that gives Claude Code persistent project memory and selected codebase context using Obsidian notes, chat imports, and Graphify knowledge graphs. Developers use it to retain decisions between sessions and retrieve relevant code information without repeatedly reading the whole repository. Its catalogue commands support this memory and code-context workflow.

lucasrosati/claude-code-memory-setup · 1,038 stars · on GitHub

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/lucasrosati/claude-code-memory-setup

Made for: Claude Code.

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/lucasrosati/claude-code-memory-setup/resume/github.svg)](https://agentmods.dev/commands/lucasrosati/claude-code-memory-setup/resume)
Your own site
<a href="https://agentmods.dev/commands/lucasrosati/claude-code-memory-setup/resume"><img src="https://agentmods.dev/badge/commands/lucasrosati/claude-code-memory-setup/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/lucasrosati/claude-code-memory-setup/resume"><img src="https://agentmods.dev/badge/commands/lucasrosati/claude-code-memory-setup/resume.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 795 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.00000 $0.00795
Opus 5.5 $0.00000 $0.00318
Sonnet 5.5 $0.00000 $0.00159
Haiku 4.5 $0.00000 $0.00080

Measured yesterday against content hash 6438762f8c7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 yesterday.

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 · 45 lines

How it starts

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

/resume — Load Context from the Previous Session

When you receive this command, do the following:

Vault detection (by project, never by a fixed path)

  1. Run this block (one Bash call) and use the printed vault= as <vault>, project= as <project>, project_dir= as <vault>/<project> and logs= as the log folder for the rest of the command:
    setopt nullglob 2>/dev/null  # zsh aborts on unmatched globs; no-op in bash
    vault=${VAULT_DIR:-$HOME/vault}
    root=$(git rev-parse --show-toplevel 2>/dev/null); root=${root:-$PWD}
    project=$(basename "$root")
    if [ -d "$vault/$project" ]; then pdir="$vault/$project"; logs="$pdir/logs"; else pdir=""; logs="$vault/logs"; fi
    echo "vault=$vault project=$project project_dir=${pdir:-NONE} logs=$logs"
    
    • The vault is $VAULT_DIR (default ~/vault). The project is the basename of the git top-level folder, or of the current directory outside git.
    • project_dir=NONE: say so, suggest creating <vault>/<project>/ (Part 1 of the guide), and load only the logs from <vault>/logs/. Don't create a vault folder.
  2. Also read the general rules in <vault>/CLAUDE.md and, if it exists, <vault>/<project>/_moc.md.

Load context

  1. Read <vault>/<project>/CLAUDE.md if it exists (the project's permanent memory, including ## Permanent facts).
  2. Split the logs in <logs>, newest first, into rich (written by /save) and automatic (stub from the SessionEnd hook, with auto-log in the tags):
    cd "<logs>" && for f in $(ls -t); do grep -qx '  - auto-log' "$f" && echo "auto $f" || echo "rich $f"; done | head -20
    
  3. Read the last 3 rich logs (or the requested number). From the automatic logs newer than the last rich one, read only the frontmatter and ## Stats: they go in one line ("since then: N short sessions, no rich log").
  4. Read the most recent entries of <vault>/<project>/architecture/decisions.md (the file can have thousands of lines: read from the end, starting at the last ## headings, not the whole file).
  5. A pending item in a log is a snapshot of the past. A deadline quoted in memory ("by 10/10") counts as pending only if the date hasn't passed.

Read the full file on GitHub · 45 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. yesterday First seen · 45 lines · 0 tokens per session scan A 6438762f8c7c

Subscribe to this mod's changes

resume is a command published in the GitHub repository lucasrosati/claude-code-memory-setup (1,038 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 795 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-10-22.

Related

Other commands, from other repositories