Security audit
Security checks for vulnerabilities and agentic risk
The UniOne workflow includes safeguards, but its automatic setup executes remote code without separate approval or clear limits on local changes.
Review setup before enabling this skill. Install a verified, fixed CLI version under your control and assess its automatic skill synchronization before first use. OOMOL processes the requested UniOne operations, so review the connected account's permissions and confirm email recipients and content. The installer payload and hosted connector implementation were not verified; the available evidence does not establish malicious behavior.
The supplied code performs remote script execution rather than any visible UniOne data operation. Installation can be a supporting implementation detail, but nothing supplied establishes that this Oomol installer supports the declared UniOne functionality. The downloaded script's specific actions cannot be determined from this command alone.
The command pipes a mutable remote script directly into bash without checking a pinned version, signature, or independently trusted checksum. HTTPS protects transport but does not prevent a compromised distribution endpoint from serving malicious code, which would execute with the agent's local privileges; 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 missing-CLI fallback directs the agent to execute remote installation scripts without first explaining local system changes or obtaining installation-specific approval. Although this is a legitimate setup dependency rather than an unrelated action, installer code can modify files and access resources available to the executing account; the listed tool restriction may constrain execution but is not a substitute for safe setup instructions.
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