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/hooksgit clone --depth 1 https://github.com/melandlabs/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/hooks)<a href="https://agentmods.dev/commands/melandlabs/openloomi/hooks"><img src="https://agentmods.dev/badge/commands/melandlabs/openloomi/hooks.svg" alt="Measured on agentmods" 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 | $0.00014 | $0.00286 |
| Opus 5 | $0.00007 | $0.00143 |
| Sonnet 5 | $0.00003 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade B, and why
hooks scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
| `install` | `install-hooks` | Merges the plugin's hook block into `~/.claude/settings.json` (preserves other plugins' hooks). | What it actually says
/openloomi:hooks [install|uninstall|status]
The plugin never auto-installs hooks. Choose a subcommand:
| Subcommand | Bridge call | Effect |
|---|---|---|
install |
install-hooks |
Merges the plugin's hook block into ~/.claude/settings.json (preserves other plugins' hooks). |
uninstall |
uninstall-hooks |
Removes only the plugin's block; idempotent. |
status |
hooks-status |
Reports whether the block is currently installed. |
Default (no argument) runs status.
node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs install-hooks
node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs uninstall-hooks
node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs hooks-status
The bridge runs merge-no-overwrite and is atomic. The Stop hook always exits 0; archive failures never block Claude Code.
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.
- 4d ago First seen · 27 lines · 14 tokens per session scan B 1fa56a9cc20e
hooks is a command published in the GitHub repository melandlabs/openloomi (1,020 stars, last pushed 4d ago), licensed Apache-2.0. It adds 14 tokens to every session and 286 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
/release
Release a new version — updates CHANGELOG, pyproject.toml, creates git tag, and pushes.
AGENTS
Per-command agent-optimized usage and structure guide.
speckit.archive
Archive a feature specification into main project memory after merge, resolving gaps and conflicts.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
speckit.extract
Extract ADRs, knowledge, and guidelines from completed specifications into dev/ documentation.