Security audit
Security checks for vulnerabilities and agentic risk
The coupon workflow has clear safeguards, but its automatic installer and undisclosed changes to other agent skills warrant review.
Prefer an already reviewed CLI installation. Require approval before running the remote installer, and review or disable its automatic agent-skill synchronization. Connecting Coupontools gives OOMOL access to the selected account; retain the skill's confirmation requirement for coupon changes. The remote installer and CLI implementation were not verified.
The only supplied command executes an external installer rather than reading or modifying Coupontools data. Although dependency installation can be a supporting implementation detail, this chunk provides no evidence that the Oomol CLI supports the declared Coupontools functionality. The downloaded script's contents and any further effects cannot be determined from the supplied code.
The command streams a mutable remote script directly into Bash without pinning a version or verifying its integrity; the PowerShell example uses an equivalent download-and-execute pattern. Although the endpoint is relevant to the documented CLI dependency, compromise of the distribution source could execute arbitrary code with the invoking user's privileges, potentially exposing accessible credentials and files.
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 setup fallback directs the agent to install software when the CLI is missing, without requiring approval or explaining that downloaded code will run with the invoking user's privileges and may change the local environment. Restricting installation to a missing-dependency error reduces exposure, but a request to operate Coupontools does not necessarily authorize local software installation.
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