Security audit
Security checks for vulnerabilities and agentic risk
The Webex workflow has clear safeguards, but its setup fallback can execute unverified downloaded code without a separate approval step.
Review this skill's setup before enabling it. Install a verified CLI release separately, check its automatic skill-installation settings, and approve local changes explicitly. Consider whether OOMOL should handle your Webex data, and retain the stated confirmations for writes and deletions. The bundled instructions were fully inspected, but the external installers and connector implementation remain unverified; no malicious intent was established.
The supplied command executes code from an Oomol CLI installation endpoint rather than performing Webex operations. Nothing in the supplied chunk establishes this installer as a supporting dependency for Webex. The downloaded script is not provided, so its further behavior cannot be determined.
The command pipes remotely fetched content directly into Bash without version pinning or independent integrity verification; the PowerShell alternative has the same trust issue. HTTPS and the apparently relevant vendor domain reduce some risks, but a compromised distribution endpoint could still execute arbitrary code with the agent's privileges and expose local files or credentials.
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 instructs the agent to install software when the CLI is missing without requiring approval for local system changes. Although conditional setup is relevant to this skill, a Webex request does not inherently authorize executing installer 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