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/setupgit 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.00023 | $0.03412 |
| Opus 5 | $0.00012 | $0.01706 |
| Sonnet 5 | $0.00005 | $0.00682 |
| Haiku 4.5 | $0.00002 | $0.00341 |
Grade A, and why
setup 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/openloomi:setup
The bridge is now an end-to-end wizard. A single setup invocation
walks the full state machine:
install OpenLoomi.app
→ launch the desktop app (`open -a <desktopMarker>`)
→ wait for the local HTTP API to come up
→ mint a guest bearer (one-tap sign-in)
→ { ready: true }
Each transition is automatic. Do not ask the user to click anything in
the GUI. The bridge only surfaces a stop condition when the next step
truly requires human action (e.g. no selected execution runtime is ready and
no direct AI provider is configured — if Claude is selected, point the user at
claude auth login; otherwise use OpenLoomi Desktop → API Settings).
Steps
- If the install needs explicit consent (the bridge returns
setup: install_attemptedis the only case where this matters — normally--yesis passed straight through), confirm with the user before re-running. - Run:
node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs setup --yes [--max-wait <ms>] - Read the JSON. The bridge writes an audit trail of what it did into
steps[]. Surface that to the user so they can see which transitions fired. - If
setup: ready→ done. - If
setup: awaiting_user_action→ the chain hit a step that genuinely needs the user (e.g.nextAction: login_openloomibutcanGuestLogin: falsebecause the local runtime didn't come up, ornextAction: configure_ai_providerbecause the runtime reports no ready selected execution provider and no per-user provider row). Explain what the user needs to do and stop.
Flags
| Flag | Default | Meaning |
|---|---|---|
--yes |
off | Pre-approve install (otherwise the bridge prompts y/N — but in Claude Code's Bash tool there is no TTY, so without --yes the install would silently cancel). |
--max-wait |
120000 | Global cap across all wait stages (in milliseconds). Defaults to 120s to absorb the first-run install + TCC prompts. |
--api-timeout |
120000 | Per-stage budget for "waiting for local API". Independent of --max-wait. |
--install-timeout |
300000 | Per-stage budget for "installing OpenLoomi". Covers download + copy on a 50 Mbps link. |
--launch-timeout |
10000 | Per-stage budget for open -a <bundle>. Almost never actually hit; included for symmetry. |
--permission-timeout |
60000 | Extra wait after --api-timeout if the desktop process is up but the API never woke up — typical macOS TCC/Accessibility prompt path. |
--bin-path |
auto | Override the discovered helper binary path (advanced). |
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 · 218 lines · 23 tokens per session scan A 7928e1ee9fb6
setup is a command published in the GitHub repository melandlabs/openloomi (1,020 stars, last pushed 9d ago), licensed Apache-2.0. It adds 23 tokens to every session and 3,412 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 이슈를 읽어 요구사항·코드 영향 범위 정리.