Security audit
Security checks for vulnerabilities and agentic risk
The Trello workflow includes clear approval safeguards, but setup can execute an unverified remote installer automatically.
Review setup before installing. Install a reviewed, pinned CLI separately and check its automatic agent-skill installation behavior. OOMOL will mediate access to the connected Trello account; connect only the intended account and retain the stated approval requirements for changes. The concern is installation control, with no artifact-backed evidence of malicious intent.
The supplied chunk executes a third-party installer rather than performing Trello operations. No evidence establishes this installation as a supporting requirement for the declared skill. The downloaded script is not supplied, so its downstream actions cannot be determined.
Piping a downloaded installer directly into Bash executes mutable remote code with the agent process's local permissions, without verifying its contents, signature, or expected digest. A compromised distribution endpoint could run arbitrary commands or steal accessible credentials; the missing-CLI condition limits exposure but does not remove the risk, and the PowerShell example has the same weakness.
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