Security audit
Security checks for vulnerabilities and agentic risk
Bird actions require appropriate approvals, but automatic CLI setup executes unverified remote code without explaining or separately approving broader local changes.
Review and install the CLI separately before use, and examine its automatic skill synchronization settings. Bird contact data and message payloads pass through OOMOL; grant only needed account permissions and retain the skill's write and deletion confirmations. The remote installer payload was unavailable for inspection. No malicious behavior was established.
The supplied code performs remote installer execution rather than any identifiable Bird operation. Nothing in the supplied material establishes this installer as a supporting dependency for Bird access. The downloaded script's contents are not provided, so its additional effects cannot be determined.
The command immediately executes whatever script the remote endpoint returns, without version pinning or independent integrity verification; the PowerShell alternative has the same weakness. HTTPS and the provider-related domain reduce some risks but do not protect against a compromised distribution endpoint or malicious installer update, which could execute code with the agent's local privileges.
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 missing-CLI fallback directs the agent to execute a remote installer without explicitly obtaining approval for local software installation or explaining its system changes. Although installation is a legitimate prerequisite and only occurs after a specific failure, it expands a Bird data request into local code execution with the agent's privileges.
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