Security audit
Security checks for vulnerabilities and agentic risk
The Slack workflow is clearly described, but setup instructs the agent to execute an unverified remote installer without a separate approval step.
Review the installation fallback before enabling this skill. Prefer installing a verified CLI yourself, or require explicit approval before downloaded setup code runs. OOMOL will mediate access to your connected Slack account, so limit its permissions and review posts and deletions. The remote installers and hosted connector implementation were not inspected; the supplied artifact does not establish malicious behavior.
The supplied code contains no Slack interaction. Its only demonstrated behavior is executing an external installer, with no evidence connecting that installation to the declared Slack functionality. The downloaded script is not supplied, so its further behavior cannot be assessed.
Piping a remotely fetched script directly into Bash executes its current contents without a pinned version or independent integrity verification; the PowerShell example has the same weakness. Compromise of the distribution endpoint could allow arbitrary code execution with the agent's local permissions, including access to available files and credentials. The legitimate connector dependency and conditional fallback reduce suspicion of malicious intent but do not eliminate this supply-chain risk.
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 missing-command fallback instructs the agent to install software locally without explicitly requesting approval or explaining that downloaded code will execute with the agent's permissions. Confirmation requirements cover Slack mutations but do not cover this local system change; restricting installation to a missing-CLI error reduces frequency, not the authorization risk.
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