Security audit
Security checks for vulnerabilities and agentic risk
The PhantomBuster workflow is coherent, but its automatic setup can execute unverified third-party code without a separate approval step.
Review the setup before enabling this skill. Prefer separately approving and verifying a specific oo release instead of allowing automatic script execution. Check its managed-skill synchronization settings, understand that PhantomBuster requests pass through OOMOL, and confirm launch or stop operations. The remote installers' exact system changes remain unverified.
The supplied code installs software from OOMOL and contains no PhantomBuster operations or evidence that this installer is a necessary supporting dependency. Remote script execution is therefore an undeclared capability in this context. The downloaded script's contents and further effects cannot be determined from the supplied chunk.
Piping a live HTTPS response directly into Bash executes remote code with the agent process's local privileges without version pinning or independent integrity verification. A compromised installer host or distribution pipeline could therefore access local files and credentials or modify the environment; HTTPS alone does not protect against a compromised publisher. This shares the installation path identified in SQP-2, and its reachability is reduced if the declared oo-only Bash restriction is enforced.
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 missing-CLI fallback directs the agent to download and execute an installer without explaining local system changes or requiring explicit installation approval. Installing a dependency crosses a different trust boundary from operating a connected PhantomBuster account, although the error-triggered fallback and declared Bash tool restriction reduce exposure.
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