@hmanlab/hl-plugins

Install curated OpenCode plugins with one command.

Install

npm install -g @hmanlab/hl-plugins

Or invoke directly via npx (no global install needed):

# OpenCode plugins
npx -y @hmanlab/hl-plugins install mmx
npx -y @hmanlab/hl-plugins install multiplayer

# Claude Code plugin
npx -y @hmanlab/hl-plugins install mmx-claude

Usage

hl-plugins install [plugin]      # install one or all default plugins
hl-plugins uninstall [plugin]    # remove plugin(s)
hl-plugins list                  # show known plugins + install state
hl-plugins status [plugin]       # per-plugin diagnostic report
hl-plugins update [plugin]       # re-copy files + bump dependencies
hl-plugins help                  # show all commands

The install flow is idempotent and the config merge is additive — your other OpenCode plugins, MCP servers, providers, and permission settings are left untouched.

Available plugins

| Plugin | Description | Requires | |---|---|---| | @hmanlab/mmx | Image, video, music, speech, search, vision, and quota via MiniMax | mmx-cli + MiniMax Token Plan | | @hmanlab/mmx-claude | Claude Code MCP adapter for MiniMax multimodal tools | mmx-cli + bun | | @hmanlab/multiplayer | Real-time multiplayer for OpenCode | None |

To install a plugin's dependency, the CLI runs the contract's requires[].install for you (e.g. npm install -g mmx-cli). When the plugin needs credentials, the install flow prompts for the API key (input is hidden) or accepts --key / the contract's auth.envVar for CI/automation.

Documentation

Full docs live in the monorepo:

• Architecture — install flow, plugin contract
• Command reference — every flag and exit code
• Adding a plugin — drop a folder, no CLI changes needed

Security

The install flow runs the contract's shell commands on your machine. Review the hl-plugins field in each plugin's package.json before installing. API keys are passed as separate argv elements (no shell interpolation). Full notes in SECURITY.md.

License

MIT