OpenLoomi is an open-source desktop AI coworker that connects work tools, gathers context, and highlights decisions or actions needing attention. It is for people managing work across multiple apps, and its catalogue add-ons extend the resident desktop for agent frameworks such as Claude Code, Codex, OpenCode, Hermes, and OpenClaw.
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 melandlabs/openloomi/plugin install openloomiWrote 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/melandlabs/openloomi/memory)<a href="https://agentmods.dev/commands/melandlabs/openloomi/memory"><img src="https://agentmods.dev/badge/commands/melandlabs/openloomi/memory/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/melandlabs/openloomi/memory"><img src="https://agentmods.dev/badge/commands/melandlabs/openloomi/memory.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.00026 | $0.00941 |
| Opus 5.5 | $0.00010 | $0.00376 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 83 lines · 26 tokens per session scan A 34468173d9d4
memory is a command published in the GitHub repository melandlabs/openloomi (1,037 stars, last pushed 24d ago), licensed Apache-2.0. It adds 26 tokens to every session and 941 once invoked, about $0.0001 per session on Opus 5.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
speckit.archive
Archive a feature specification into main project memory after merge, resolving gaps and conflicts.
memory-init
Initialize local memory store + vector index for this project.
speckit.archive.run
Archive a feature specification into main project memory after merge, resolving gaps and conflicts.
speckit.retrospect.run
Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
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.