Security audit
Security checks for vulnerabilities and agentic risk
The Unthread workflow requires approval for data changes, but its setup directs the agent to execute unverified downloaded code without asking first.
Review setup before installing. Install a verified, version-pinned oo CLI yourself and explicitly approve local installation changes. OOMOL mediates access to your connected Unthread account; retain the required confirmations for changes and deletion. Consider disabling the CLI's automatic skill synchronization using its documented control. The remote installers and hosted connector implementation were not verified. [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md)
The supplied chunk performs remote script execution rather than Unthread data operations. No code or context establishes that the Oomol installer is a supporting dependency for Unthread. The installer's downstream actions cannot be determined from the supplied chunk.
The command pipes a remotely fetched, unpinned script directly into Bash without an independent integrity or authenticity check. If the distribution endpoint or its publishing pipeline is compromised, the script could execute arbitrary code with the invoking user's privileges; HTTPS protects transport but does not prevent a compromised publisher from serving malicious content.
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 fallback setup instructs the agent to execute a downloaded shell or PowerShell installer without explicitly warning about local code execution or requiring approval for installation. Although triggered only when the CLI is missing, this expands a request to operate on Unthread data into running third-party code with the agent's local privileges.
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