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.
git clone --depth 1 https://github.com/reganomalley/claudiaWrote 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.
[](https://agentmods.dev/commands/reganomalley/claudia/resume)<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.
<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>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.
| Model | Per session | Once 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 |
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.
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:
-
Check if
$ARGUMENTSmatches a registered project. Read~/.claude/claudia-projects.json(the registry). If$ARGUMENTSmatches a project name or path, use that project.cdto its path and do single-project resume. -
Check if we're at
~(home directory) with no arguments. If so, show the multi-project dashboard (see below). -
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:startto create one, orcdinto 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}.jsonfor stack info - Run
git -C {path} log --oneline -1for last commit - Run
git -C {path} status --shortfor 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
-
Gather context from all sources. Check these in order, reading whatever exists:
Project context (primary):
- Read project-scoped context: check
~/.claude/claudia-projects.jsonfor a key matching this directory, then read~/.claude/claudia-projects/{key}.json - Fall back to
~/.claude/claudia-context.jsonif 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-*.mdfiles in the current working directory (pick the most recent) - Look for
session-notes*.md,SESSION.md, orHANDOFF.mdin the current directory - Check
~/.claude/projects/for any recent session transcripts
- Read project-scoped context: check
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.
- 8d ago First seen · 111 lines · 25 tokens per session scan A fac4930bfe9d
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.
Other commands, from other repositories
context
A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.
bm
Ask basemind anything about the current codebase — outlines, refs, callers, git history, blame, diffs, docs, memory.
context-load
Carga de contexto al inicio de sesión. Lee estado del workspace, decisiones recientes, último session save y actividad Git para arrancar con el big picture.
cache-invalidate
Invalidación selectiva de capas de caché con rollback seguro.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
vouch-propose-from-pr
Distill a merged PR into vouch claim proposals.