Security audit
Security checks for vulnerabilities and agentic risk
The Ringover features fit the stated purpose, but the dependency setup can execute unchecked downloads and make undisclosed changes to other agents’ skills.
Review and approve the CLI installation separately, using a verified version. Before running it, consider setting OO_SKILLS_SYNC_DISABLED=1 to prevent startup changes to agent skills, as documented in the [CLI settings](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Use limited Ringover permissions and understand that OOMOL processes the connector requests. The exact remote installer payload remains unverified.
The supplied code performs no visible Ringover searches or data reads. Its sole action is executing an Oomol-hosted installer, which can modify the local environment. Nothing in the supplied chunk establishes this installation as a supporting implementation detail for Ringover access. The installer's further behavior cannot be determined from this snippet.
Piping an HTTPS response directly into bash executes whatever the installer endpoint serves without pinning or verifying the artifact. Compromise of the distribution infrastructure could therefore lead to arbitrary code execution and access to local data under the invoking account; HTTPS does not protect against a compromised publisher or endpoint. This overlaps with SQP-2 rather than representing an independent attack path.
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 execution of downloaded shell or PowerShell scripts without requiring integrity verification or explicit approval for software installation. Although this is a legitimate dependency setup path and only applies when the CLI is missing, it can execute compromised installer content with the invoking user's permissions and modify the local system.
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