Security audit
Security checks for vulnerabilities and agentic risk
The Tavily workflow is coherent, but its required CLI can persistently change other agents’ installed skills without this skill explaining that behavior.
Review the CLI’s installation and skill-sync behavior before using this integration. Prefer a verified, pinned installation and disable startup skill synchronization before the first invocation if you want to avoid changes to other agents; the publisher documents OO_SKILLS_SYNC_DISABLED=1 in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). OOMOL mediates requests and provider credentials. No malicious intent was established, but the remote installers and downloaded executable were not verified.
The declared purpose concerns Tavily, but the code executes an installer hosted on an Oomol domain without showing any connection to Tavily. This is a materially different action, not an established supporting implementation detail. The remote script's contents and further effects cannot be determined from the supplied chunk.
The supplied code performs a CLI login rather than the declared Tavily operations. Authentication could be a supporting implementation detail, but the chunk provides no evidence that oo auth login authenticates to Tavily or supports the described functionality. The mismatch assessment is limited to the supplied code; the login destination and credential handling are not established.
The setup command pipes a remotely fetched, mutable script directly into Bash without pinning or integrity verification; the PowerShell alternative follows the same download-and-execute pattern. Compromise of the distribution endpoint could execute arbitrary code with the invoking user's privileges, potentially exposing local credentials and files. Restricting this behavior to missing-CLI setup reduces exposure but does not establish the downloaded code's integrity.
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
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