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/rename)<a href="https://agentmods.dev/commands/sk-lim19f/hypomnema/rename"><img src="https://agentmods.dev/badge/commands/sk-lim19f/hypomnema/rename/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/sk-lim19f/hypomnema/rename"><img src="https://agentmods.dev/badge/commands/sk-lim19f/hypomnema/rename.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.00035 | $0.01024 |
| Opus 5 | $0.00017 | $0.00512 |
| Sonnet 5 | $0.00007 | $0.00205 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
rename 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 4d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running /hypo:rename. Move a page or directory and content-aware rewrite every inbound [[wikilink]] across the vault so the rename never breaks a link.
What this does
- Resolves
--fromto a page (.md) or a directory - Page mode: moves the single page, rewrites every inbound
[[old]]/[[old|alias]]/[[old#anchor]]/[[dir/old]]that resolves unambiguously to it - Directory mode: relocates the whole subtree (carrying non-
.mdassets) and rewrites inbound full-slug and dir-relative links for every moved page - Skips append-only time records (journal / session-log / weekly / archive / postmortems / root
log.md) and immutablesources/*as link sources - Reports ambiguous bare links it refuses to auto-rewrite, and refuses a merge/renumber into an existing destination
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 — Dry-run first
Always run the dry-run (no --apply) before writing anything:
node ${CLAUDE_PLUGIN_ROOT}/scripts/rename.mjs \
[--hypo-dir="<path>"] \
--from=<slug|rel|dir> \
--to=<slug|rel|dir> \
[--json]
Options:
--from— the page slug / relative path, OR an existing directory to relocate--to— the new name. A bare name renames in place within the same directory; a path with/moves across directories. For a directory--from,--tomust be a fresh (non-existing) directory in the same top-level area--json— machine-readable result (recommended so you can present a precise summary)--apply— perform the move + rewrites (Step 4)
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.
- 4d ago Changed cf3f8f9750b1
- 9d ago First seen · 80 lines · 35 tokens per session scan A a5f0c3d93562
rename is a command published in the GitHub repository sk-lim19f/Hypomnema (11 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,024 once invoked, about $0.0002 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
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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.