claude

A Claude Code plugin that connects Claude Code to a locally running OpenLoomi system, which stores agent memory and provides a local runtime. It mirrors Claude's lifecycle and archives each completed session stop into OpenLoomi.

In plain words
What is it for?
Installing the connection, syncing Claude Code lifecycle events with OpenLoomi, and saving completed-session information to local memory.
Why use it?
It keeps session records in the local OpenLoomi system without reading or transferring the AI provider's API keys.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add melandlabs/openloomi
agentmods
npx agentmods add plugins/melandlabs/openloomi/claude
Clone the repo
git clone --depth 1 https://github.com/melandlabs/openloomi

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured The manifest loads nothing itself; its 11 skills, 10 commands, 8 hooks cost 1,448 tokens a session between them.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

claude 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.

plugins/claude/.claude-plugin/plugin.json · 21 lines

What it actually says

{
  "name": "openloomi",
  "version": "0.9.0",
  "description": "Connect Claude Code to your local OpenLoomi runtime. One-command install, mirror Claude's lifecycle onto the Loomi Pet, and auto-archive every Stop into your OpenLoomi memory. Talks to your local OpenLoomi over HTTP and the OpenLoomi helper CLI. AI provider config is owned by OpenLoomi itself — this plugin never reads or pushes API keys.",
  "author": { "name": "OpenLoomi" },
  "homepage": "https://openloomi.ai",
  "repository": "https://github.com/melandlabs/openloomi/tree/main/plugins/claude",
  "license": "Apache-2.0",
  "keywords": [
    "openloomi",
    "memory",
    "pet",
    "anthropic",
    "claude-code",
    "local-first",
    "loops"
  ],
  "commands": "./commands",
  "skills": "./skills"
}
Changes

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.

  1. 3d ago First seen · 21 lines scan A fb6f32edc601

Subscribe to this mod's changes

claude is a plugin published in the GitHub repository melandlabs/openloomi (1,020 stars, last pushed 9d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.