Security audit
Security checks for vulnerabilities and agentic risk
The Beebole workflow has approval safeguards, but its fallback setup runs unverified remote installation code without a separate approval step.
Review setup before enabling this skill. Prefer a reviewed, version-pinned CLI installation, require approval for local installation, and review or disable the CLI's automatic skill synchronization. OOMOL will broker your Beebole requests and credentials. Keep the existing payload confirmations for account changes. The remote installer was unavailable for inspection.
The supplied command executes an Oomol-hosted installer rather than performing any visible Beebole operation. Although installation can be a supporting implementation detail, this chunk establishes no relationship between that installer and the declared Beebole functionality. The fetched script is not supplied, so its further behavior cannot be determined.
Piping the HTTPS response directly into bash executes mutable remote content without a pinned version or independent integrity verification; the PowerShell alternative has the same issue. Compromise of the installer delivery path could execute arbitrary code with the agent's local privileges, exposing files and credentials, although the documented OOMOL dependency makes legitimate installation intent plausible.
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 directs the agent to execute a downloaded installer without explicitly obtaining approval for local software installation or explaining that remote code will run with the agent's local privileges. Requiring a command-not-found error limits when this occurs, but a request to operate Beebole does not necessarily authorize these local 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