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/querygit 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/query)<a href="https://agentmods.dev/commands/sk-lim19f/hypomnema/query"><img src="https://agentmods.dev/badge/commands/sk-lim19f/hypomnema/query.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.00038 | $0.00494 |
| Opus 5 | $0.00019 | $0.00247 |
| Sonnet 5 | $0.00008 | $0.00099 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
query 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.
What it actually says
You are running /hypo:query. Answer a question by searching the wiki and synthesizing from relevant pages.
What this does
- Searches
pages/andprojects/for pages relevant to the query - Reads and cross-references the top matches
- Synthesizes a grounded answer citing
[[page-slug]]links
Step 1 — Understand the query
Ask the user what they want to know if it was not provided in the command invocation.
Step 2 — Search
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.
Run full-text search:
node ${CLAUDE_PLUGIN_ROOT}/scripts/query.mjs \
--q="<query terms>" \
[--hypo-dir="<path>"] \
[--limit=10]
Step 3 — Read relevant pages
Read index.md first to understand the page catalog, then read the top-scoring pages returned by the search script (up to 5).
Step 4 — Synthesize answer
Write a clear, concise answer that:
- Cites source pages as
[[slug]]links - Notes confidence level if any source is speculative
- Flags if no relevant pages were found ("Hypomnema does not currently have a page on this topic.")
If the query surfaces a gap, offer to create a new page or run /hypo:ingest on a relevant source.
Step 5 — Offer follow-ups
After answering, suggest 1–2 related pages the user might want to read next.
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 First seen · 56 lines · 38 tokens per session scan A efb21da31dee
query is a command published in the GitHub repository sk-lim19f/Hypomnema (10 stars, last pushed 5d ago), licensed MIT. It adds 38 tokens to every session and 494 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
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
neo-review
Get Neo's code review with semantic matching against past findings in memory. Use on a diff or module before merge, especially where earlier mistakes in this codebase are likely to recur. Skip for formatting, lint-catchable issues, and single-line changes.