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/graphgit 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/graph)<a href="https://agentmods.dev/commands/sk-lim19f/hypomnema/graph"><img src="https://agentmods.dev/badge/commands/sk-lim19f/hypomnema/graph.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.00035 | $0.00605 |
| Opus 5 | $0.00017 | $0.00302 |
| Sonnet 5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
graph 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running /hypo:graph. Generate a link dependency graph from wiki pages.
What this does
- Scans
pages/andprojects/for all.mdfiles - Extracts
[[wikilink]]references between pages - Outputs an adjacency graph in JSON, Mermaid, or DOT format
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 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 the graph script
node ${CLAUDE_PLUGIN_ROOT}/scripts/graph.mjs \
[--hypo-dir="<path>"] \
[--format=json|mermaid|dot] \
[--min-edges=<n>]
Options:
--format=json(default) — adjacency list with in/out degree counts--format=mermaid— Mermaidgraph TDdiagram (paste into a Markdown code block)--format=dot— Graphviz DOT format--min-edges=<n>— only include nodes with at least N total edges
Step 3 — Present results
- For JSON: summarise the top 10 most-connected nodes (highest in+out degree), then offer to show the full output.
- For Mermaid: wrap the output in a
\``mermaid` code block so it renders in the chat. - For DOT: show the raw output and suggest pasting it into a Graphviz renderer.
If --min-edges was not specified and there are more than 50 nodes, suggest re-running with --min-edges=2 to focus on well-connected pages.
Step 4 — Insights
After displaying results, offer one or two observations:
- Pages with high in-degree are hub pages — consider linking to them from new pages.
- Pages with zero edges are isolated — suggest adding cross-links or running
/hypo:crystallize.
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 · 55 lines · 35 tokens per session scan A 261519e620d9
graph is a command published in the GitHub repository sk-lim19f/Hypomnema (10 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 605 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.