Security audit
Security checks for vulnerabilities and agentic risk
The Ozon features fit the stated purpose, but setup executes downloaded code without clear user approval or integrity checks.
Review and approve CLI installation separately before allowing setup to run. Check its bundled-skill installation behavior, and limit the connected Ozon account to needed read permissions. OOMOL mediates access to seller data. The remote installer payloads were unavailable for inspection, so their exact local changes remain unverified.
The supplied command executes a remote installer rather than searching or reading Ozon data. Although dependency installation can be a supporting implementation detail, the supplied chunk establishes no connection between this installer and the declared Ozon functionality. The remote script's contents and any further effects are not available for assessment.
Piping a remotely fetched script directly into bash executes whatever the endpoint returns with the invoking user's privileges, without a pinned version or independent integrity verification. A compromised distribution endpoint could therefore expose local files and credentials or enable persistent changes; HTTPS and the legitimate setup purpose do not eliminate this supply-chain risk. The Windows download-and-evaluate command has the same underlying weakness.
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 instructs the agent to execute an installer without first explaining its local effects or obtaining explicit installation approval. A request to read Ozon data does not inherently authorize executing downloaded software or modifying the local environment, although the conditional fallback reduces 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