Security audit
Security checks for vulnerabilities and agentic risk
The fallback setup directs the agent to execute downloaded installers without a separate approval step or integrity check.
Review and approve the CLI installation separately before allowing fallback setup. Prefer a reviewed, version-pinned installation. Connecting Freshdesk lets OOMOL handle access to account and ticket data; the bundled instructions do not establish the external CLI or installers' implementation.
The supplied code performs remote script execution rather than searching or reading Freshdesk data. Nothing in the supplied chunk establishes that the Oomol installer is a supporting dependency for Freshdesk access. The downloaded script's contents are not supplied, so its additional behavior cannot be determined.
Piping an HTTPS response directly into bash executes mutable remote code with the agent's local privileges, without version pinning or independent integrity verification. Compromise of the distribution endpoint could expose accessible files and credentials or alter the host; the PowerShell example presents the same risk. The official-looking dependency context and missing-CLI condition do not establish the downloaded code's safety.
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 the agent to execute downloaded code without explaining that installation can modify the host or requiring user approval. Conditioning installation on a command failure reduces exposure, but a request to read Freshdesk data does not itself authorize local software installation; the Bash tool restriction may limit execution if strictly enforced.
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