Code Pluginsource linked
Nebius Token Factoryv1.3.1
Nebius Token Factory provider plugin for OpenClaw — 44+ open-source models via a single endpoint
Community code plugin. Review compatibility and verification before install.openclaw plugins install clawhub:@colygon/openclaw-nebiusLatest release: v1.3.1Download zip
Capabilities
- configSchema
- Yes
- Executes code
- Yes
- HTTP routes
- 0
- Providers
- nebius
- Runtime ID
- nebius
Compatibility
- Built With Open Claw Version
- 2026.4.5
- Min Gateway Version
- 2026.3.24-beta.2
- Plugin Api Range
- >=2026.3.24-beta.2
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, openclaw.plugin.json, SKILL.md, and the bundled dist code all describe a model provider that talks to https://api.tokenfactory.nebius.com/v1 and requires a single Nebius API key. The declared providerAuthEnvVars and SKILL.md metadata both request only NEBIUS_API_KEY, which is proportionate to the plugin's stated function.
Instruction Scope
Runtime instructions focus on installing/configuring the OpenClaw plugin, setting the NEBIUS_API_KEY, and enabling the plugin. They direct the agent/user to edit OpenClaw-specific paths (~/.openclaw/...), to add the provider to plugins.allow, and to restart the gateway — all within the expected scope. One notable assumption: the setup uses macOS-specific guidance (launchctl setenv and references to LaunchAgent). That will not work on Linux/Windows; the SKILL.md/SETUP.md do not provide alternative instructions for other OSes.
Install Mechanism
No external install/remote download spec is included; the plugin is intended to be installed via OpenClaw's plugin install command (clawhub:@colygon/openclaw-nebius). Bundled code (dist/) is present in the package, and there are no unusual download URLs or archive extraction steps in the package files provided.
Credentials
Only one credential is required (NEBIUS_API_KEY) and it is justified by the plugin's purpose. The SKILL.md and openclaw.plugin.json both declare this same env var. The instructions ask to place the key in the OpenClaw auth-profiles.json and to set an environment variable so the gateway can read it — both are reasonable for an API-key-based provider.
Persistence & Privilege
The plugin does not request elevated platform privileges or always:true. It instructs modifications to OpenClaw user config (auth-profiles.json and plugins.allow) and to restart the gateway — expected behavior for adding a provider. The skill does not request system-wide credentials beyond the provider API key.
Assessment
This package appears to do what it says: register a Nebius provider and require a single Nebius API key. Before installing: 1) Confirm you obtained the API key from studio.nebius.ai and trust that endpoint. 2) Back up any existing ~/.openclaw/agents/main/agent/auth-profiles.json and your current plugins.allow value before modifying them. 3) If you are not on macOS, do not run the launchctl instructions — use the equivalent method for your OS (systemd service env or other) so the OpenClaw gateway can access the key. 4) Verify the plugin source (the repo URL in package.json) and inspect the dist/index.js if you want to double-check network endpoints; it references only api.tokenfactory.nebius.com. 5) Installing third‑party plugins grants them the ability to be invoked by agents — this plugin is user-invocable and not forced (always:false), but consider whether you want the plugin enabled for autonomous agent actions in your environment.Verification
- Tier
- source linked
- Scope
- artifact only
- Summary
- Validated package structure and linked the release to source metadata.
- Commit
- a24f094
- Tag
- main
- Provenance
- No
- Scan status
- clean
Tags
- latest
- 1.3.1