Security audit
Security checks for vulnerabilities and agentic risk
Wufoo changes require user approval, but setup can execute remote installers and introduce broader agent changes that this skill does not explain.
Review and install a verified CLI release separately, and decide whether to allow its automatic bundled-skill synchronization. Connect only the intended Wufoo account and review submission payloads before approving them. The remote installer contents remain unverified; the artifact does not establish malicious intent.
The supplied code performs remote installer execution rather than a Wufoo operation. Although installing a CLI could be a supporting implementation detail, nothing in this chunk establishes a connection between the Oomol installer and the declared Wufoo functionality. The downloaded script's contents are not supplied, so its downstream behavior cannot be determined.
Piping the HTTPS installer directly into bash executes mutable remote content without version pinning or integrity verification. HTTPS protects transport but not against a compromised publishing endpoint or malicious installer update, which could execute code with the invoking account's privileges; the missing-CLI condition reduces exposure but does not remove this 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 the agent to execute downloaded shell or PowerShell code without explaining local-system changes or requiring explicit installation approval. Although conditional setup is legitimate, a routine Wufoo request could thereby trigger arbitrary code execution with the agent's local privileges if the installer supply chain is compromised.
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