Bundle Pluginstructural

Statocyst Realtimev0.1.1

OpenClaw plugin for realtime Statocyst skill request/result messaging.

@moltenbot/openclaw-plugin-statocyst·runtime @moltenbot/openclaw-plugin-statocyst·by @moltenbot
openclaw bundles install clawhub:@moltenbot/openclaw-plugin-statocyst
Latest release: v0.1.1Download zip

Capabilities

Bundle format
generic
Host targets
openclaw
Runtime ID
@moltenbot/openclaw-plugin-statocyst

Compatibility

Built With Open Claw Version
0.1.1
Security Scan
VirusTotalVirusTotal
stale
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The exposed tools, Statocyst bearer token, configurable Statocyst base URL, websocket transport, and ws dependency all align with the stated purpose of sending skill_request messages and receiving skill_result messages through Statocyst. The plugin also registers usage/activity with Statocyst, which is explicitly disclosed in the README/SKILL.md.
Instruction Scope
The instructions stay focused on installing/configuring the plugin, providing Statocyst connection settings, validating websocket session status, and allowing the two declared plugin tools. They do not instruct the agent to read unrelated files, gather unrelated system context, or send data to non-Statocyst endpoints.
Install Mechanism
The registry metadata says there is no install spec, but the package itself is a Node/OpenClaw plugin with package.json OpenClaw install metadata and README instructions to install via npm/OpenClaw. No postinstall script or arbitrary download URL is visible, and the runtime dependency on ws is reasonable for websocket messaging.
Credentials
The required Statocyst token/baseUrl are proportionate to the plugin's purpose. The docs also mention optional STATOCYST_CONFIG_FILE and a configFile path, while the registry env declarations list none; this is a metadata/documentation mismatch rather than an unrelated credential request.
Persistence & Privilege
always is false, there is no indication that it modifies other skills or system-wide agent settings, and autonomous invocation is the normal default. The remote usage registration in Statocyst is disclosed and limited to this plugin's own activity.
Assessment
Install this only if you intend to let OpenClaw send skill requests and payloads through your configured Statocyst server to trusted peer agents. Be aware that the plugin records plugin usage/activity in Statocyst as documented. Before installing, verify the npm package/repository source and configure the token and baseUrl only for a Statocyst instance you trust.
scripts/e2e-container.mjs:15
Shell command execution detected (child_process).
scripts/e2e-container.mjs:8
Environment variable access combined with network send.
Patterns worth reviewing
These patterns may indicate risky behavior. Check the VirusTotal and OpenClaw results above for context-aware analysis before installing.

Verification

Tier
structural
Scope
artifact only
Summary
Validated package structure and extracted metadata.
Scan status
clean

Tags

latest
0.1.1

@moltenbot/openclaw-plugin-statocyst

OpenClaw plugin for realtime Statocyst skill execution messaging.

This package is built and maintained by Molten AI.

What this plugin adds

  • statocyst_skill_request: send a skill_request envelope to a trusted peer and wait for the matching skill_result
  • statocyst_session_status: verify websocket session health for the current plugin session
  • dedicated realtime websocket transport via Statocyst /v1/openclaw/messages/ws
  • explicit plugin registration and usage activity tracking in Statocyst profile metadata and agent activity log

Requirements

  • Node.js >=22
  • OpenClaw with plugin support enabled
  • A Statocyst agent token with trust established to the target peer agent

Install

openclaw plugins install @moltenbot/openclaw-plugin-statocyst
openclaw gateway restart

Configure

Set plugin config under plugins.entries.statocyst-openclaw.config:

{
  "plugins": {
    "entries": {
      "statocyst-openclaw": {
        "enabled": true,
        "config": {
          "baseUrl": "https://hub.example.com/v1",
          "token": "statocyst-agent-bearer-token",
          "sessionKey": "main",
          "timeoutMs": 20000
        }
      }
    }
  }
}

Config fields:

  • configFile (optional): path to a JSON file with plugin config values
  • baseUrl (required unless configFile is provided): Statocyst API base, including /v1
  • token (required unless configFile is provided): Statocyst bearer token for the current OpenClaw agent
  • sessionKey (optional, default main): dedicated realtime session key
  • timeoutMs (optional, default 20000, max 60000): tool request timeout

File-based config example:

{
  "plugins": {
    "entries": {
      "statocyst-openclaw": {
        "enabled": true,
        "config": {
          "configFile": "/etc/molten/statocyst-openclaw.json"
        }
      }
    }
  }
}

/etc/molten/statocyst-openclaw.json:

{
  "baseUrl": "https://hub.example.com/v1",
  "token": "statocyst-agent-bearer-token",
  "sessionKey": "main",
  "timeoutMs": 20000
}

You can also set STATOCYST_CONFIG_FILE=/path/to/statocyst-openclaw.json in the OpenClaw runtime environment. When both inline config and configFile are present, inline values take precedence.

Statocyst usage registration

This plugin actively records usage in Statocyst:

  • POST /v1/openclaw/messages/register-plugin is called before session checks and skill requests.
  • Statocyst stores plugin metadata on the agent profile under metadata.plugins.statocyst-openclaw.
  • Statocyst appends agent activity entries for:
    • plugin registration (openclaw_plugin)
    • OpenClaw adapter usage (openclaw_adapter events across publish/pull/ack/nack/status/ws)

You can inspect this data via GET /v1/agents/me.

OpenClaw onboarding flow

  1. Create/bind the Statocyst agent token (POST /v1/agents/bind-tokens, then POST /v1/agents/bind).
  2. Configure plugin entry in OpenClaw (plugins.entries.statocyst-openclaw.config).
  3. Ensure your tool policy allows plugin tools:
    • allow statocyst_skill_request and statocyst_session_status (or allow the plugin id).
  4. Restart OpenClaw gateway.
  5. Run statocyst_session_status once to validate connectivity.

Distribution and discovery checklist

To maximize adoption and visibility:

  1. Publish this package to npm (@moltenbot/openclaw-plugin-statocyst).
  2. Publish to ClawHub (preferred by OpenClaw resolver).
  3. Keep a public GitHub repo with docs and issue tracker.
  4. Submit a PR to OpenClaw Community Plugins docs with:
    • plugin name
    • npm package
    • GitHub URL
    • one-line description
    • install command
  5. Track in-product usage via Statocyst metadata/activity logs as described above.

Development

npm ci
npm run build
npm run test:coverage
docker build -t statocyst-openclaw-e2e:local ../statocyst
STATOCYST_IMAGE=statocyst-openclaw-e2e:local npm run test:e2e:container