Security audit
Security checks for vulnerabilities and agentic risk
The Bolna read actions fit the stated purpose, but setup can execute unverified remote software without a clear user approval step.
Review the setup before installing. Install a verified CLI release yourself, require approval for installation changes, and review or disable its automatic skill synchronization. Connecting Bolna lets the agent retrieve workspace information and execution logs through OOMOL. No malicious behavior was established, but the remote installer's exact contents remain unverified.
The supplied command installs software by executing remote code rather than searching or reading Bolna data. No connection is shown that would establish this installer as a supporting implementation detail for the declared purpose. The downloaded script's contents and further effects are not available for assessment.
The command pipes a mutable remote script directly into Bash without pinning or independently verifying its contents; the PowerShell alternative uses the same execution pattern. A compromised distribution endpoint could therefore execute arbitrary code with the invoking process's permissions, although the file provides no evidence that the endpoint is currently malicious.
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
On a missing-CLI error, the skill directs installation through downloaded code without first explaining the system changes or obtaining explicit approval. This expands a read-only Bolna request into local code execution with the agent's operating-system permissions; the conditional trigger reduces exposure but does not authorize that expansion.
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