status

status is a command for coding agents from melandlabs/openloomi. It costs 15 tokens per session (183 once invoked), scanned A, original, Apache-2.0.

A read-only command that reports whether the OpenLoomi connection to Claude Code is set up and ready.

In plain words
What is it for?
Use it to check the connection mode, readiness, next action, authentication probe, and whether OpenLoomi hooks are installed.
Why use it?
It shows the current setup state and explains what needs attention without changing anything.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the openloomi plugin — 11 skills, 10 commands, 8 hooks shipped together

About the project

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.

melandlabs/openloomi · 1,021 stars · on GitHub

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.

agentmods
npx agentmods add commands/melandlabs/openloomi/status
Clone the repo
git clone --depth 1 https://github.com/melandlabs/openloomi

Or install openloomi, the plugin that ships this one along with the rest of its 11 skills, 10 commands, 8 hooks.

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

agentmods badge for status

README.md
[![agentmods](https://agentmods.dev/badge/commands/melandlabs/openloomi/status.svg)](https://agentmods.dev/commands/melandlabs/openloomi/status)
Your own site
<a href="https://agentmods.dev/commands/melandlabs/openloomi/status"><img src="https://agentmods.dev/badge/commands/melandlabs/openloomi/status.svg" alt="Measured on agentmods" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 183 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.00183
Opus 5 $0.00008 $0.00092
Sonnet 5 $0.00003 $0.00037
Haiku 4.5 $0.00002 $0.00018

Measured 5d ago against content hash 93a23045a087, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

status 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 5d 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/commands/status.md · 26 lines

What it actually says

/openloomi:status

Run:

node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs setup-status --json

Print the JSON to the user verbatim. Highlight:

  • mode
  • ready
  • nextAction (when ready is false)
  • reason (debug-friendly code)
  • nativeRuntime (the runtime's claude CLI auth probe result — the plugin never inspects AI provider env vars)
  • hooksInstalled (whether /openloomi:hooks install has been run)

Do not change anything; this command is read-only.

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. 5d ago First seen · 26 lines · 15 tokens per session scan A 93a23045a087

Subscribe to this mod's changes

status is a command published in the GitHub repository melandlabs/openloomi (1,021 stars, last pushed 5d ago), licensed Apache-2.0. It adds 15 tokens to every session and 183 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.