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/usagegit 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.00013 | $0.00271 |
| Opus 5 | $0.00006 | $0.00135 |
| Sonnet 5 | $0.00003 | $0.00054 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
usage 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.
What it actually says
/openloomi:usage
Run:
node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs usage
Print the resulting JSON to the user. Real response shape:
configured(boolean) — provider is configuredproviderSince— ISO 8601 timestamp when the provider was first setcurrentProvider—{ providerType, model, enabledSince }trackedEndpoints— array of endpoint names being trackedtotals—{ inputTokens, outputTokens, totalTokens }aggregated over the tracked periodrunCount— number of runs in the tracked periodfirstRunAt/lastRunAt— ISO 8601 timestampstrackedProviders— array of provider names includedasOf— ISO 8601 timestamp of when the summary was computed
If the API is unreachable the bridge returns
code: "API_UNREACHABLE" — surface that and prompt the user to start
OpenLoomi Desktop.
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 · 31 lines · 13 tokens per session scan A 0aa9f3206cc4
usage is a command published in the GitHub repository melandlabs/openloomi (1,020 stars, last pushed 9d ago), licensed Apache-2.0. It adds 13 tokens to every session and 271 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 이슈를 읽어 요구사항·코드 영향 범위 정리.