Security audit
Security checks for vulnerabilities and agentic risk
Sunsama actions require approval, but setup executes unchecked downloads and the required CLI can silently add persistent skills to other agents.
Review and install a verified CLI release yourself before enabling this skill. Decide whether you want its additional agent skills; the publisher documents OO_SKILLS_SYNC_DISABLED=1 to prevent startup skill synchronization. [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Connecting Sunsama authorizes OOMOL-mediated account access. The downloaded installers remain unverified; no artifact evidence establishes malicious intent.
The supplied command executes an Oomol-hosted installer and shows no Sunsama MCP functionality or evidence that this installation supports Sunsama access. This is materially different from the declared purpose. The downloaded script is not supplied, so its additional behavior cannot be assessed.
The command executes the current contents of a remote URL immediately, without a pinned version, signature check, or independently trusted digest. HTTPS protects transport but does not protect against a compromised publishing endpoint, which could deliver code capable of accessing local files and credentials; this is the same underlying installation risk identified by SQP-2.
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 pipe remotely downloaded scripts directly into Bash or PowerShell without integrity verification or explicit approval for local code execution. If the distribution endpoint or its delivery infrastructure is compromised, an agent following these instructions could execute attacker-controlled code with its local permissions; conditional setup limits exposure but does not eliminate it.
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