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.
npx agentmods add commands/sk-lim19f/hypomnema/initgit clone --depth 1 https://github.com/sk-lim19f/HypomnemaWrote 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/init)<a href="https://agentmods.dev/commands/sk-lim19f/hypomnema/init"><img src="https://agentmods.dev/badge/commands/sk-lim19f/hypomnema/init.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 | $0.00033 | $0.01128 |
| Opus 5 | $0.00016 | $0.00564 |
| Sonnet 5 | $0.00007 | $0.00226 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade B, and why
init 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Merges hook entries into `~/.claude/settings.json` (idempotent) How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running /hypo:init. Set up a new personal wiki powered by Hypomnema.
If the user passes a remote URL (e.g. /hypo:init --from-remote [email protected]:user/wiki.git), skip the wizard and go directly to Step 2a — From Remote.
What this does
- Creates the Hypomnema directory structure (
pages/,projects/,sources/, etc.) - Copies baseline template files (
index.md,hot.md,log.md,hypo-config.md,SCHEMA.md,hypo-guide.md) - Installs Claude Code hooks for automatic context injection
- Merges hook entries into
~/.claude/settings.json(idempotent) - Optionally sets up git with a remote
Step 1 — Wizard
Ask the following questions one at a time. Use the default if the user presses Enter.
-
Wiki directory
"Where should your wiki live? [~/hypomnema]" Default:
~/hypomnema -
Install hooks
"Install Claude Code hooks for automatic context injection? [yes]" Default: yes
-
Codex hooks — ask only if the user answered yes to hooks AND
~/.codex/exists"Also install Codex-compatible hooks in ~/.codex/hooks/? [yes]" Default: yes Skip this question if hooks=no or
~/.codex/does not exist. -
Git remote (optional)
"Git remote URL for sync/backup? (Enter to skip)" Default: skip
Step 2a — From Remote (skip wizard) {#step-2a}
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 reinstall instead of guessing the cache layout.
If the user provided --from-remote <url>, run:
node ${CLAUDE_PLUGIN_ROOT}/scripts/init.mjs \
--from-remote="<url>" \
--hypo-dir="<hypo-dir>" \
[--no-hooks] \
[--codex]
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 First seen · 104 lines · 33 tokens per session scan B cfb7e3cee58e
init is a command published in the GitHub repository sk-lim19f/Hypomnema (10 stars, last pushed 5d ago), licensed MIT. It adds 33 tokens to every session and 1,128 once invoked, about $0.0002 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
git
Git operations with intelligent commit messages and workflow optimization.
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.