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/upgrade)<a href="https://agentmods.dev/commands/sk-lim19f/hypomnema/upgrade"><img src="https://agentmods.dev/badge/commands/sk-lim19f/hypomnema/upgrade.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.00029 | $0.00911 |
| Opus 5 | $0.00015 | $0.00456 |
| Sonnet 5 | $0.00006 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade B, and why
upgrade scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **settings.json**: checks if all hook registrations are present in `~/.claude/settings.json` How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running /hypo:upgrade. Check if the installed Hypomnema wiki is out of date and offer to apply updates.
What this checks
- SCHEMA version: compares
~/hypomnema/SCHEMA.mdversion against the package's current version - Hook files: checks if any hooks in
~/.claude/hooks/are stale or missing - settings.json: checks if all hook registrations are present in
~/.claude/settings.json
Step 1 — Run script
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.
If the user specified a Hypomnema directory, pass it as --hypo-dir="<path>". Otherwise omit the flag.
Step 2 — Run upgrade check
node ${CLAUDE_PLUGIN_ROOT}/scripts/upgrade.mjs [--hypo-dir="<path>"]
Show the output verbatim.
Plugin installs: if the output begins with
ℹ Plugin install detected, the core hooks, slash commands, andsettings.jsonwiring are managed by the Claude Code plugin loader — not by/hypo:upgrade. Do not run--applyexpecting it to update them (it intentionally skips those to avoid double-registering every hook). To upgrade the plugin itself:/plugin marketplace update hypomnemathen/reload-plugins. Then run--applyanyway: the vault's git pre-commit hook holds an absolute path baked in at init time, and reloading the plugin does not move it, so without that step every wiki commit keeps running the install you had when you first ran init.--applyin plugin mode applies vault-side migrations (SCHEMA,.hypoignore), refreshes package metadata, and still syncs any vault extensions — but does not install the core hooks/commands/settings (the plugin provides those).
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.
- 2d ago Changed 0149d92e53d3
- 7d ago First seen · 66 lines · 29 tokens per session scan B d18cbf4f8faa
upgrade is a command published in the GitHub repository sk-lim19f/Hypomnema (10 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 911 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.