Security audit
Security checks for vulnerabilities and agentic risk
The subscriber-management workflow is clearly scoped, but its fallback setup executes an unverified remote installer without a separate approval step.
Review setup before enabling this skill. Install a verified CLI release deliberately, check its automatic agent-skill synchronization settings, and retain approval requirements for subscriber changes and deletions. OOMOL mediates account access. The remote installer contents remain unverified.
The supplied code contains only remote installer execution and no Mobile Text Alerts operations. Nothing supplied establishes the Oomol installer as a necessary supporting dependency, so its execution is an undeclared capability involving an inconsistent external resource. The downloaded script's further behavior cannot be determined from this chunk.
Piping a mutable remote installation script directly into Bash executes its contents without version pinning or integrity verification. HTTPS protects transport but does not protect against compromise of the distribution endpoint or a malicious script update, which could execute arbitrary code with the agent's local permissions; the PowerShell example has the same underlying 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 directs the agent to install software by executing remotely downloaded scripts without first obtaining explicit approval for local code execution and system changes. Limiting this to a missing-CLI error reduces exposure, but approval to manage Mobile Text Alerts data does not inherently authorize local software installation; execution would have the agent process's permissions.
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