Security audit
Security checks for vulnerabilities and agentic risk
The MQTT workflow is clearly scoped, but its setup can execute changing third-party installation code without separate user approval.
Review the CLI installation separately before allowing setup. Prefer a reviewed, version-pinned release with verified integrity, and check its automatic agent-skill synchronization settings. MQTT traffic uses the disclosed OOMOL integration; confirm the destination topic, payload, and effect before publishing. Only the skill instructions were bundled, so the downloaded installer's exact effects remain unverified.
The supplied chunk performs remote script execution rather than MQTT operations. Nothing in the chunk establishes that this installation is a supporting implementation detail required for MQTT access. The downloaded script is not provided, so its specific system changes cannot be assessed.
The supplied chunk contains only a login command and shows no MQTT interaction or connection between that login and an MQTT service. Authentication could support an MQTT workflow, but no such workflow is present in the supplied code.
The curl-to-bash command immediately executes whatever code the installation endpoint returns, without a pinned version or independent integrity verification. HTTPS protects transport but does not prevent a compromised distribution endpoint from supplying code that accesses local files, credentials, or other resources available to the invoking user; the PowerShell alternative has the same underlying risk.
oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux
The fallback setup directs the agent to execute downloaded shell or PowerShell code without explaining its host-level effects or requiring explicit installation approval. Although this is a legitimate dependency setup path rather than evidence of malicious intent, a missing CLI can trigger system changes beyond the user's requested MQTT operation.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.
- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.
## Resources