Security audit
Security checks for vulnerabilities and agentic risk
This ScraperAPI integration needs review because setup executes unverified installation scripts and can introduce additional agent skills without clearly requesting approval.
Review and approve a fixed CLI release separately before allowing setup. Check its automatic skill synchronization settings and connect only the intended account. Requests pass through OOMOL and ScraperAPI and may incur charges. The remote installer and server-side implementation were not included in the reviewed artifact.
The supplied code installs software from an Oomol-hosted endpoint; it does not make a ScraperAPI request. Nothing supplied establishes this installation as a supporting implementation detail for ScraperAPI. The remote script's contents and any additional effects cannot be determined from this chunk.
The supplied chunk performs only a CLI login operation and contains no ScraperAPI interaction or evidence that this authentication supports ScraperAPI. Its observable purpose therefore differs materially from the declared purpose.
Piping an HTTPS download directly into bash executes mutable remote content without first verifying its integrity or reviewing it. A compromised distribution endpoint or malicious installer update could execute arbitrary code and access local data under the agent's privileges; the legitimate setup purpose does not remove this supply-chain 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 install software without an explicit user-approval checkpoint or disclosure of local changes. Although conditional and related to the task, installation can execute arbitrary code with the agent's local privileges; the declared oo-only tool allowance may limit execution if enforced but does not make these instructions safe.
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