Skip to main content
The Modellix Plugin packages everything your coding agent needs to generate images and videos with Modellix: the official Modellix skill, model discovery guidance, default model choices, credential handling, and retry rules that match the CLI exit codes. The repository follows the Open Plugins specification, so the same layout installs into Claude Code, Codex, Cursor, OpenClaw, OpenCode, Pi, Hermes, and any Agent Skills host.

Plugin or skill

The repository ships in two shapes. Pick the one your host supports.
If you only need the Agent Skill, see the Skill guide, which covers the standalone modellix-skill repository as well.

What the plugin provides

  • A CLI-first workflow: modellix-cli doctormodel run --waittask download
  • Automatic REST fallback when the CLI is not installed
  • Sensible default models when you do not name one
  • Model discovery through modellix-cli model list and model describe, plus the live model index at llms.txt
  • Retry and error guidance aligned with CLI exit codes, including paid-submission safety rules
  • Credential handling for MODELLIX_API_KEY and saved CLI auth profiles

Requirements

The plugin works without the CLI by calling the REST API directly, but the CLI gives your agent faster task submission, built-in waiting, and safer downloads.

Install as a plugin

Install:
Update:
You can also use the /plugin UI, then run /reload-plugins if the plugin does not appear.For local development against a clone:

Install as a skill

When your host has no plugin marketplace, or you only want skills/modellix, install the Agent Skill instead:
The Skill guide covers skill installs for skills.sh, ClawHub, OpenCode, Cursor, Pi, Hermes, and Smithery.

Configure your API key

Every install shape reads the same credential.
The CLI resolves the key in this order: --api-key, then MODELLIX_API_KEY, then the selected saved profile.
  • REST calls always require MODELLIX_API_KEY.
  • The CLI can use the environment variable or a saved profile created by modellix-cli auth login or modellix-cli init.
  • In Cursor, you can set the key as the MODELLIX_API_KEY plugin variable.
  • In Hermes, prefer ~/.hermes/.env or the secure prompt shown when the skill loads.
Prefer session-only keys and persist them only when you intend to. Never commit an API key to a repository or print it in logs.

Verify the install

Confirm the environment first, then generate one asset end to end.
1

Check the CLI and credentials

doctor reports the Node.js version, the API-key source, API connectivity, and your team balance without printing the key.
2

Ask your agent to generate something

The plugin routes the request through the CLI, picks a default model, and waits for the task to finish.
3

Confirm the output

The agent downloads results into your working directory. To reproduce the same flow manually:

Supported task types

Default models

When you do not name a model, the plugin uses these defaults: Name any other model in your prompt to override the default. To discover and inspect models:
Request-body schemas come from each model’s documentation. Follow the docs_url returned by model describe, or the links in llms.txt.

How the plugin runs tasks

Understanding these rules helps you predict what your agent will do:
  1. It prefers the CLI when installed, and falls back to the REST API otherwise.
  2. It uses model run --wait or task wait instead of hand-written polling loops.
  3. It never blindly retries a paid model run after an unknown submission outcome. It checks modellix-cli task history first.
  4. It may use the helper scripts bundled in skills/modellix/scripts/, and falls back to plain CLI commands if a helper fails.
  5. It treats modellix-cli --help and the npm package as the source of truth for CLI behavior.

Troubleshooting

Next steps

Skill

Install the Agent Skill on its own.

CLI

Learn the modellix-cli commands the plugin runs.

REST API

Call Modellix directly without the CLI.

Pricing

Review model pricing before running paid tasks.