Security audit
Security checks for vulnerabilities and agentic risk
The Callingly operations have clear approval controls, but setup directs the agent to execute downloaded installers without separate approval or integrity verification.
Review and approve CLI installation separately, preferably using a verified release. Review its automatic skill synchronization before running it. OOMOL mediates Callingly requests and credentials; retain the exact-payload and deletion approval requirements. The remote installers were unavailable for inspection.
The supplied command performs no visible Callingly operation. Its sole behavior is executing an installer hosted by Oomol. Although dependency installation can be a supporting implementation detail, the supplied content establishes no relationship between this installer and the declared Callingly functionality. The downloaded script's further effects cannot be determined from this chunk.
The curl-to-bash command immediately executes a mutable remote script without a pinned version or independently verified integrity; the PowerShell alternative follows the same pattern. Although OOMOL is a relevant dependency and HTTPS protects transport, compromise of the distribution endpoint could yield arbitrary execution with the agent's local permissions, exposing accessible files and 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
When the CLI is missing, the skill directs the agent to install it without requiring approval for executing downloaded code or modifying the local environment. The confirmation requirements cover Callingly state changes, not local installation, so a routine service request could trigger consequential actions beyond the user's intended scope.
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