Security audit
Security checks for vulnerabilities and agentic risk
The Vonage actions have approval checks, but setup executes unverified remote code and under-discloses changes to other agent skills.
Review and install the CLI separately before using this skill, and disable startup skill synchronization if you do not want other agent skills added or refreshed. Confirm each SMS recipient, message, and potential charge. OOMOL mediates the connected account; its backend and the remote installer payloads were not verified in this review.
The supplied command executes an Oomol-hosted installer rather than performing the declared Vonage operations. Nothing in the supplied chunk establishes that this installation is a supporting dependency for Vonage functionality. The downloaded script's contents and further effects are not shown.
Piping a mutable remote installer directly into bash executes its contents without prior inspection, version pinning, or cryptographic artifact verification. HTTPS protects transport but does not protect against compromise of the publisher or distribution endpoint, which could yield arbitrary code execution under the user's account; the PowerShell alternative has the same 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 fallback setup directs execution of downloaded shell or PowerShell scripts without explaining the local-code-execution risk or requiring explicit installation approval. Installation is conditional and relevant to the workflow, which reduces exposure, but a compromised installer could still execute arbitrary commands with the invoking user's 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