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/melandlabs/openloomi/memorygit clone --depth 1 https://github.com/melandlabs/openloomiWhat 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.00026 | $0.00941 |
| Opus 5 | $0.00013 | $0.00470 |
| Sonnet 5 | $0.00005 | $0.00188 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
memory 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 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.
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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/openloomi:memory
Thin doorway into the
openloomi-memory sub-skill.
- With a
<query>argument → runssearch-allacross local memory files, the knowledge base (RAG), and recent insights. - With no argument → lists the most recent 7 days of insights
(
list-insights --days=7) so the user can see what's already been captured.
For everything else (filter by channel, get a single document / insight, create / update / delete, time-travel queries, living connections, entity registry) say "memory search", "knowledge base", "insights" — the sub-skill's frontmatter triggers on those phrases and walks Claude through the right subcommand.
The CLI lives at
${CLAUDE_PLUGIN_ROOT}/skills/openloomi-memory/scripts/openloomi-memory.cjs
and auto-reads the bearer token from ~/.openloomi/token.
Steps
-
With query — run a comprehensive search:
node ${CLAUDE_PLUGIN_ROOT}/skills/openloomi-memory/scripts/openloomi-memory.cjs \ search-all "<query>"Aggregate results from
memory(local files),knowledge(RAG), andinsights. Print top 5 from each source with file path / doc id / insight id and a short preview. If the user wants more, run the same with--limitraised, or fall through to a specific source via the sub-skill'ssearch-memory/search-knowledge/list-insightscommands. -
Without query — list recent insights:
node ${CLAUDE_PLUGIN_ROOT}/skills/openloomi-memory/scripts/openloomi-memory.cjs \ list-insights --days=7Print the most recent 10 (or all if fewer than 10) with their
type,groups,time, and a shortcontentpreview. -
If the user asks for a specific source after seeing results, dispatch to the matching subcommand:
Source Subcommand Local files search-memory "<query>" [--directory=<subdir>]Knowledge base search-knowledge "<query>"orlist-documents/get-document <id>Insights list-insights [--days=N] [--channel=<gmail|telegram|...>] [--keyword=<k>...]
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 · 83 lines · 26 tokens per session scan A 34468173d9d4
memory is a command published in the GitHub repository melandlabs/openloomi (1,020 stars, last pushed 9d ago), licensed Apache-2.0. It adds 26 tokens to every session and 941 once invoked, about $0.0001 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-30.
Other commands, from other repositories
statuswt
You are checking the status of all active worktree task files in the project.
finishwt
You are finishing a worktree task.
release
Command "release" from CIrcui-try/Circuit, covering 절차, 1단계: 사전 확인, 2단계: 변경사항 수집, 직전 release 시점 (main의 가장 최근 release pr merge 시각) and 그 시점 이후 develop으로 머지된 pr 목록.
review-and-fix
로컬 변경사항을 직접 리뷰하고 문제점 수정 후 커밋·푸시.
takeoff
항공기 이륙 4단계 — develop 리베이스 → push → PR 생성 (원격 영향).
boarding
항공기 이륙 1단계 — Linear 이슈를 읽어 요구사항·코드 영향 범위 정리.