Security audit
Security checks for vulnerabilities and agentic risk
The FFHub workflow is coherent, but its setup fallback tells the agent to execute an unverified remote installer without a separate user approval step.
Review the setup fallback before installing. Install the required CLI through a separately reviewed process and require approval before the agent runs an installer. Understand that OOMOL mediates access to your FFHub account, and retain confirmation for task creation. The bundled instructions show no malicious intent, but the external installers' exact effects remain unverified.
The supplied command installs software from an Oomol domain rather than performing FFHub data operations. Nothing in the supplied content establishes this installer as a supporting FFHub dependency. The remote script's contents and further effects are not visible.
The command downloads a mutable external script and immediately executes it with the invoking user's privileges, without version pinning or independent integrity verification. Compromise of the installer delivery infrastructure could therefore expose local credentials or modify files; HTTPS and the legitimate dependency context reduce some risks but do not establish the script's integrity. The PowerShell alternative has the same weakness, although an enforced Bash(oo *) restriction may prevent either installation path from running.
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 tells the agent to install software after a missing-command error without first explaining the local execution and system changes or obtaining approval. Although limited to first-time setup, this expands a remote FFHub task into local software installation; the write-confirmation rule covers FFHub state rather than clearly covering this operation.
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