Security audit
Security checks for vulnerabilities and agentic risk
The Zyte functions fit the stated purpose, but setup can execute an unverified remote installer and introduce broader changes to your agent environment.
Review the setup behavior before installing. Use a separately reviewed CLI installation, require approval before remote installers run, and check automatic skill synchronization settings. OOMOL mediates requests using your connected Zyte credentials, and usage may incur charges. The external installer and live connector implementation were not validated.
The supplied command does not interact with Zyte or retrieve data through its API. It executes an installation script hosted on an unrelated domain, with no demonstrated connection to the declared functionality. The downloaded script's further behavior cannot be determined from this chunk.
The only supplied command performs authentication rather than the declared Zyte API operations. Authentication could be a supporting implementation detail if tied to Zyte, but the supplied content establishes no such relationship. The mismatch is based on this behavioral divergence, not the absence of declared permissions.
The command pipes a remotely fetched, unpinned script directly into Bash without integrity verification or review; the PowerShell example uses the same download-and-execute pattern. If the installer distribution is compromised, attacker-controlled code can execute with the agent process's privileges and access its files or credentials; HTTPS and the legitimate setup purpose do not eliminate 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 first explaining the system changes or obtaining explicit user approval. Although this is relevant setup rather than malicious scope expansion, a request to read Zyte data does not necessarily authorize running an installer or modifying the local environment.
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