Security audit
Security checks for vulnerabilities and agentic risk
The httpSMS workflow is clearly described, but its setup fallback executes unverified downloaded code without a separate approval step.
Review and install a verified CLI release yourself before using this skill, and prevent the agent from running its automatic installer fallback. Check the CLI's bundled-skill synchronization settings. OOMOL will mediate access to your connected httpSMS account, including private messages. Keep confirmation enabled for sending and deletion. The remote installer and hosted connector implementation were not verified.
The supplied command contains no httpSMS operation and instead runs an installer from cli.oomol.com. Nothing supplied establishes that this installer is a supporting dependency for httpSMS. The downloaded script's contents are unavailable, so its additional effects cannot be determined.
The supplied code performs only a CLI login and contains no identifiable httpSMS interaction. Authentication could be a supporting implementation detail if tied to httpSMS, but the supplied chunk establishes no such connection and instead has a materially different observable purpose.
Piping a remotely fetched installer directly into bash executes mutable external content without a pinned version, integrity verification, or review; the PowerShell alternative has the same weakness. Compromise of the script's distribution infrastructure could expose local credentials and files or enable persistent compromise, although exploitation requires the setup fallback to be reached and execution to be permitted.
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-CLI fallback directs installation by executing downloaded shell or PowerShell code without requiring explicit approval for local system changes. Although conditional and relevant to setup, this can expand an ordinary httpSMS request into arbitrary code execution with the agent's user privileges; the action-confirmation rules only explicitly cover httpSMS state changes.
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