Security audit
Security checks for vulnerabilities and agentic risk
The BigML workflow is coherent, but setup can execute unverified downloaded software without a clear approval step.
Review dependency setup before use. Prefer a separately verified CLI installation and require approval for installation or changes to other agent skills. OOMOL mediates the BigML connection and requests. Keep the documented confirmations for writes and deletions. The remote installer and hosted connector implementation were not verified; no malicious behavior was established.
The supplied chunk performs no visible BigML operations. Its sole action is to download and execute an Oomol installer, and nothing provided establishes this as a supporting BigML dependency. This is an inconsistent resource and an undeclared installation capability. The remote script's contents and any further effects cannot be determined from the supplied code.
The only supplied command initiates authentication and contains no BigML-specific target or operation. Authentication could be a supporting implementation detail, but the supplied chunk provides no connection to BigML and implements none of the declared functionality. This assessment does not imply that the login is malicious.
The curl-to-bash command immediately executes mutable remote content with the invoking user's privileges, without version pinning or independent integrity verification. Compromise of the installer distribution path could enable credential theft or local file modification; HTTPS helps protect transport but does not establish installer integrity, and the PowerShell example 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 setup workflow directs the agent to execute downloaded shell or PowerShell code without first explaining local system changes or obtaining installation-specific approval. A missing dependency can therefore turn a BigML request into local code execution; the conditional setup requirement reduces exposure but does not establish informed authorization.
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