Security audit
Security checks for vulnerabilities and agentic risk
The Botsonic workflow is coherent, but automatic setup executes unverified remote code and can introduce additional persistent agent skills without clearly disclosing those changes.
Review and approve a verified CLI installation before allowing setup, and disable startup skill synchronization if you only want this Botsonic integration. Connect only the account access you need and retain confirmation for writes. OOMOL mediates the integration; live installer code and hosted connector behavior were not verified.
The supplied code installs software from an Oomol endpoint and contains no visible Botsonic functionality or evidence that this installer supports Botsonic operations. Executing the remote installer is a materially different capability from the declared data-management purpose. The downloaded script's contents and further effects are not available for assessment.
Piping the remote installer directly into Bash executes its contents without a review or integrity-verification step. HTTPS protects transport but does not protect against a compromised publisher or installer endpoint, which could deliver code that steals local credentials or modifies files; the conditional setup limits exposure but does not remove this 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 instructs the agent to execute remotely downloaded shell or PowerShell code without explaining the execution risk or requiring approval for local installation. Although setup occurs only when the CLI is missing, it can execute arbitrary code with the invoking user's privileges if the installer is compromised; confirmation requirements for Botsonic writes do not cover this local action.
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