Security audit
Security checks for vulnerabilities and agentic risk
The SERPHouse integration is coherent, but its setup can execute changing remote installers without clear user approval or verification.
Review and install the CLI yourself before use, and require approval for installer execution or additional agent-skill changes. OOMOL handles the connected SERPHouse credentials, and searches may consume credits. The concern is uncontrolled setup execution; the artifact does not show exfiltration or destructive intent. Installer contents and backend behavior remain unverified.
The supplied code performs remote software installation, not SERPHouse searching or data retrieval. No connection between the Oomol installer and the declared SERPHouse functionality is shown, so this cannot be established as a supporting implementation detail. The downloaded script's contents and further effects are not available for assessment.
The supplied chunk performs only a login operation, not SERPHouse searching or data retrieval. Authentication could be a supporting implementation detail, but nothing in the supplied content identifies oo as a SERPHouse client or connects this login to the declared service.
Piping a mutable remote script directly into Bash executes its contents with the agent process's local permissions, without version pinning or independent integrity verification. HTTPS protects transport but does not prevent a compromised distribution endpoint or release pipeline from supplying code that steals accessible secrets or modifies local files; the PowerShell installer 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
A missing CLI triggers instructions to execute a remote installer without first obtaining approval for local software installation and its system changes. Although this is a legitimate dependency setup step, a request to read SERPHouse data does not inherently authorize arbitrary installer execution on the user's machine.
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