Security audit
Security checks for vulnerabilities and agentic risk
The skill requires approval for Cubox changes, but its setup can execute unpinned remote installers without separate user approval.
Review before installing. Preinstall a trusted, version-pinned CLI through an approved process and require separate approval for software installation or changes to other agent skills. Cubox requests pass through OOMOL, so review the connected account's permissions and approve each write payload. The external installers and hosted backend remain unverified; the artifact does not establish malicious behavior.
The supplied chunk performs remote installer execution rather than any visible Cubox operation. Dependency installation could be a supporting implementation detail, but the provided content does not establish that this installer supports Cubox functionality. The remote script's contents and downstream effects are not available and cannot be determined from this chunk.
Piping an HTTPS response directly into bash executes mutable remote code with the agent process's local privileges, without a pinned version or independent integrity verification. A compromised distribution endpoint could therefore execute arbitrary commands and access local data; the legitimate CLI dependency and missing-command condition limit exposure but do not eliminate it. The PowerShell installation 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 a downloaded installer without explaining its local execution privileges or obtaining installation-specific approval. Although dependency installation is relevant to Cubox access, consent to a Cubox operation does not necessarily authorize local software installation and system changes.
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