Security audit
Security checks for vulnerabilities and agentic risk
ReferralHero operations have clear safeguards, but setup can execute downloaded installation code without separate user approval.
Review and approve CLI installation separately before allowing this skill to perform setup. Prefer a pinned, independently verified installation and review any bundled agent skills it installs. OOMOL mediates access to your ReferralHero account, so use appropriately limited permissions and retain the required write/delete confirmations. The Review verdict concerns setup control; the artifact does not establish malicious behavior.
The supplied chunk contains no ReferralHero operations or evidence connecting the Oomol installer to the declared purpose. Although installation can be a supporting implementation detail, this chunk only downloads and executes an unrelated service's installer. The downloaded script's contents and any further effects cannot be determined from the supplied code.
Piping an HTTPS response directly into bash executes mutable remote code with the invoking user's permissions, without a pinned version or independent integrity verification. Compromise of the installer distribution could therefore expose local files and credentials or enable persistence; its legitimate setup purpose and missing-CLI condition reduce exposure but do not eliminate this supply-chain 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 instructs the agent to execute downloaded installation scripts without explaining their system-level effects or obtaining installation-specific approval. Although triggered only when the CLI is absent, this expands a ReferralHero data task into local software installation, outside the skill's explicit confirmation requirements for ReferralHero writes and deletions.
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