Security audit
Security checks for vulnerabilities and agentic risk
The SafetyCulture workflow has clear safeguards, but its fallback setup directs the agent to execute an unverified remote installer without a separate approval step.
Review and approve the CLI installation separately before use, including any automatic installation of other agent skills. SafetyCulture requests pass through OOMOL, so consider its access to your account and data. The skill requires confirmation before account changes, but the external installer and hosted connector implementation were not verified.
The supplied code performs remote script execution rather than any demonstrated SafetyCulture operation. Although dependency installation can be a supporting implementation detail, nothing supplied establishes this installer as a SafetyCulture dependency. The downloaded script's contents and further effects cannot be determined from this snippet.
Piping a remotely fetched installer directly into bash executes mutable remote content with the agent process's local privileges, without an integrity check or review boundary. HTTPS and the legitimate relationship to the tooling provider reduce suspicion of malicious intent, but a compromised distribution endpoint could still deliver arbitrary code; the PowerShell alternative 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 external tooling when the CLI is missing without explicitly requesting approval for executing downloaded code or changing the local environment. The missing-command condition limits exposure, but authorization to perform a SafetyCulture task does not necessarily authorize installing software on the host.
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