Security audit
Security checks for vulnerabilities and agentic risk
Review is needed because this Envoy reader directs unchecked software installation and uses a CLI that can also change persistent agent skills.
Install and verify a specific CLI release yourself before use. Disable its automatic skill synchronization using OO_SKILLS_SYNC_DISABLED=1, as documented in the [CLI command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Connect only the Envoy account you intend OOMOL to access. Remote installer contents and hosted connector code remain outside the verified artifact.
The supplied command performs remote script execution for an Oomol installer, with no visible Envoy interaction. This introduces installation and arbitrary remote-code execution capabilities not represented by the declared read/search purpose. The downloaded script's specific effects cannot be determined from this chunk.
The command pipes a mutable network response directly into Bash without pinning or independently verifying the downloaded code; the PowerShell alternative has the same execution pattern. Compromise of the installer distribution could execute attacker-controlled commands with the agent's local privileges, exposing accessible files and credentials despite Envoy tokens being injected server-side.
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 software after a missing-command error without explicitly obtaining approval or explaining that downloaded code will modify the local environment. This crosses the boundary from reading Envoy data to executing installation code; the conditional trigger limits exposure, but does not establish user authorization.
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