Security audit
Security checks for vulnerabilities and agentic risk
The Xata read workflow is coherent, but setup runs unverified remote code and leaves broader agent changes undisclosed.
Review setup before installing. Prefer a verified CLI version installed under your control, and use a Xata key limited to needed reads. Confirm you accept OOMOL brokering the connection. The current [CLI reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md) documents OO_SKILLS_SYNC_DISABLED=1 to prevent automatic skill synchronization. The remote installer and hosted connector implementation were not verified.
The supplied command performs remote installer execution, with no visible Xata interaction. Installing software from Oomol is materially different from the declared Xata data-access purpose, and the chunk provides no evidence that this is a supporting dependency for that purpose. The downloaded script's further behavior cannot be determined from the supplied code.
The supplied chunk only invokes a login command; it contains no Xata search or read operation. Authentication could be a supporting implementation detail, but nothing in this chunk establishes that oo auth login authenticates to Xata or supports the declared functionality.
Piping an HTTPS download directly into bash executes mutable remote content without a verification or review step. Compromise of the installer distribution infrastructure could result in arbitrary code execution with the agent process's permissions; the legitimate dependency and conditional setup reduce exposure but do 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
The setup instructions direct the agent to execute downloaded shell or PowerShell code without explaining that this grants the installer the current user's execution privileges or requiring explicit installation approval. The missing-CLI condition limits exposure, but requesting Xata reads does not necessarily authorize system changes or execution of mutable third-party code.
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