Security audit
Security checks for vulnerabilities and agentic risk
The BotStar controls are clear, but setup needs review because it executes downloaded code without verification or a separate approval step.
Review and approve CLI installation separately, preferably using a verified fixed release. Check its automatic skill synchronization settings before running it. OOMOL mediates your BotStar access; connect an appropriately limited account and retain the required confirmations for writes, publishing, and deletion. The installer scripts were not available for content verification, so their complete effects remain uncertain.
The supplied chunk contains only an Oomol installer command and no BotStar interaction. Although dependency installation can be a supporting implementation detail, the provided content establishes no connection between this installer and BotStar functionality. The downloaded script's contents and any additional effects are not visible.
Piping a remotely fetched script directly into Bash executes mutable network-delivered code with the agent process's local privileges, without integrity verification or review. HTTPS and the apparently relevant vendor domain reduce some exposure but do not prevent a compromised distribution endpoint from serving code that steals accessible data or modifies the system; the PowerShell 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 fallback directs the agent to install local software after a missing-command error without explicitly obtaining approval for system changes. Although setup is relevant and conditional, a request to operate BotStar does not necessarily authorize downloading and executing a local installer; the actual execution also depends on the host's tool permissions.
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