Security audit
Security checks for vulnerabilities and agentic risk
The Hoop data access fits its purpose, but setup directs the agent to execute an unverified online installer without a clear user approval step.
Review and install a verified CLI release yourself before enabling this skill, and check its automatic skill synchronization settings. Connecting Hoop entrusts OOMOL with access to the connected account. The complete bundled Markdown was inspected; the scanner's reference gaps do not indicate missing artifact files. Remote installer and hosted-service behavior remain outside the verified artifact.
The supplied command performs remote installer execution, not Hoop data searching or reading. Installing software from an unrelated service is a materially different, undeclared capability. The downloaded script is not supplied, so its additional effects cannot be determined.
The command pipes a mutable remote script directly into Bash without version pinning or independent integrity verification; the PowerShell alternative has the same execution pattern. If the distribution endpoint or release pipeline is compromised, attacker-controlled code could execute with the invoking user's permissions, exposing local data and credentials; HTTPS and the missing-CLI prerequisite reduce some exposure but do not establish script integrity.
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
A missing CLI triggers instructions to execute downloaded shell or PowerShell code without first obtaining approval for installation or explaining its system effects. Although conditional setup is relevant to the skill, authorization to read Hoop data does not necessarily authorize executing an installer with the agent's local permissions.
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