Security audit
Security checks for vulnerabilities and agentic risk
The Riveter integration is coherent, but its automatic setup can execute unverified installers and introduce broader agent changes without clearly explaining them.
Review and approve the CLI installation separately before enabling automatic setup. Prefer a verified, fixed release, and consider disabling managed-skill synchronization using the documented OO_SKILLS_SYNC_DISABLED control. OOMOL brokers the connection and requests, and scraping may consume credits. The installer payload and hosted implementation were not verified; no malicious behavior was established.
The supplied command performs remote script execution from an Oomol endpoint. Nothing in the supplied code connects that installation to Riveter or implements the declared search/read functionality, so this is not established as a supporting implementation detail. The downloaded script's further behavior cannot be determined from this chunk.
Piping an HTTPS response directly into Bash executes whatever the endpoint supplies without pinning or verifying the installer. A compromised installer or distribution service could access local files and credentials or modify the environment; the missing-CLI condition reduces exposure but does not protect execution integrity.
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 setup instructions direct execution of downloaded shell and PowerShell scripts without an explicit approval checkpoint or artifact verification. Although restricted to a missing-CLI fallback, this can turn a read-oriented task into arbitrary code execution with the agent process's permissions if the distribution endpoint or installer is compromised.
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