Security audit
Security checks for vulnerabilities and agentic risk
The property-search workflow fits its purpose, but its fallback setup directs the agent to execute an unverified remote installer without a clear user approval step.
Review before enabling automatic setup. Install and verify the CLI yourself, inspect its bundled-skill installation and update behavior, and explicitly approve local changes. OOMOL mediates the connected account, and usage may require credit. The remote installer payload remains unverified; the review found no artifact-backed deception or malicious behavior.
The supplied chunk performs no Stream Estate search or read operation. Its sole behavior is executing an Oomol-hosted installer, and nothing supplied establishes that installation as a supporting implementation detail for Stream Estate access. The downloaded script's contents and any further effects are not available for assessment.
The command pipes an unpinned remote script directly into Bash, giving whatever code the endpoint returns the privileges of the executing user without prior verification. A compromised distribution endpoint or malicious installer update could execute arbitrary commands and access local files or credentials; the PowerShell alternative has the same weakness. The legitimate dependency and missing-CLI condition limit exposure but do not establish the downloaded code's 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
A missing-command error triggers instructions to install third-party software without first obtaining approval for remote code execution or local system changes. Although installation supports the legitimate workflow, a request to read property data does not itself authorize installing software; this finding overlaps with SC2.
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