Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sk-lim19f/Hypomnema/plugin install hypoWrote 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/sk-lim19f/hypomnema/resume)<a href="https://agentmods.dev/commands/sk-lim19f/hypomnema/resume"><img src="https://agentmods.dev/badge/commands/sk-lim19f/hypomnema/resume.svg" alt="Measured on agentmods" 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.00028 | $0.00575 |
| Opus 5 | $0.00014 | $0.00287 |
| Sonnet 5 | $0.00006 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00057 |
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 3d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running /hypo:resume. Load the session state for an active project and pick up where you left off.
What this does
- Reads
projects/<name>/session-state.md(next tasks) - Reads
projects/<name>/hot.md(what was done last session) - Offers to continue from the last stopping point
Step 1 — Resolve project
If the user named a project in the command invocation, use that. Otherwise, run:
node ${CLAUDE_PLUGIN_ROOT}/scripts/resume.mjs [--hypo-dir="<path>"] [--project=<name>]
Bundled scripts here run via ${CLAUDE_PLUGIN_ROOT}/scripts/. To resolve that package root: if ${CLAUDE_PLUGIN_ROOT} is already an absolute path, use it; otherwise read pkgRoot from ~/.claude/hypo-pkg.json (only when non-empty and the target script exists under it); otherwise use the hypo@hypomnema (or legacy hypomnema@hypomnema) installPath in ~/.claude/plugins/installed_plugins.json; if none resolve, stop and tell the user to run hypomnema upgrade --apply (or /hypo:upgrade on a plugin install) or reinstall instead of guessing the cache layout.
When --project is omitted, the script prefers the project whose working_dir contains the current directory (cwd-first); if nothing under the current directory matches, it falls back to the most recently active project from hot.md.
Step 2 — Present session state
Show the output from the script:
[WIKI: ...]notice, if present, first and verbatim. It names uncommitted changes elsewhere in the vault (another project, or unattributable to any project) that are not this session's scope. Do not fold this line into the project summary or fetch/edit the paths it names without the user's explicit instruction.- Project name
- Next tasks from
session-state.md - Background from
hot.md(what was done last session, condensed)
Step 3 — Offer to continue
After presenting the state, ask:
"Ready to pick up from here? Which task should we start with?"
If the session-state lists numbered tasks, offer them as options. Start immediately once the user selects one.
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.
- 3d ago Changed · +1 lines ceca5ec6e666
- 4d ago Changed 7487bfff3fa4
- 8d ago First seen · 51 lines · 28 tokens per session scan A 3b4e219ba104
resume is a command published in the GitHub repository sk-lim19f/Hypomnema (10 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 575 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
standup
Quick daily standup from today's Claude Code sessions — grouped by project, with cost and errors.
fire-todos
Capture, list, and manage todos during work sessions.
gsd:resume-work
Resume work from previous session with full context restoration.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
ops
Weekly operations loop — triage the inquiry inbox, advance the CRM pipeline, sweep open PRs across repos, and surface the content plan. Loads the ops skill.
standup
A command that creates a daily stand-up report by summarizing recent work, planned tasks, calendar events, and blockers.