Security audit
Security checks for vulnerabilities and agentic risk
The Tisane integration is coherent, but automatic setup executes unverified software and may install additional agent skills without clearly informing you.
Preinstall a verified CLI release and prevent automatic execution of the fallback installers. Review whether you want its additional agent skills; upstream documents OO_SKILLS_SYNC_DISABLED=1 to disable startup skill synchronization. [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md) Submit only text you permit OOMOL and Tisane to process. The remote installers and exact CLI build could not be verified.
The supplied code performs remote script execution, not Tisane searching or data retrieval. Nothing in the chunk establishes that installing the Oomol CLI is a supporting dependency for the declared purpose. The downloaded script's contents and further effects are not available for assessment.
The setup instructions pipe a mutable remote script directly into Bash without verifying its contents, signature, or expected digest; the Windows alternative uses the same download-and-execute pattern. Compromise of the distribution endpoint could execute attacker-controlled code with the agent's local privileges, although the missing-CLI prerequisite and declared Bash tool restriction may limit reachability in environments that enforce it.
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 workflow instructs the agent to submit action payloads through the OOMOL connector to Tisane, including text or person-entity data for the listed analysis actions. Although the skill identifies the services and explains credential handling, it never warns that submitted content leaves the user's environment; its blanket characterization of untagged actions as safe reads also overlooks this privacy impact.
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