Security audit
Security checks for vulnerabilities and agentic risk
The RedFoxHub integration is coherent, but its automatic setup can execute changing remote code and introduce persistent agent skills without clearly explaining those effects.
Review and install the CLI separately before using this skill, rather than allowing automatic download-and-execute setup. Consider disabling managed-skill synchronization, documented through OO_SKILLS_SYNC_DISABLED, if you do not want additional agent skills installed. Connect only the intended account and review task payloads and charges. The remote installers and service implementations were not audited; the review concerns setup control and persistent changes, with no artifact-backed evidence of malicious intent.
The supplied chunk performs no visible RedFoxHub operations; its sole action is downloading and executing an external installer. Although installation can be a supporting implementation detail, nothing supplied establishes this installer as a RedFoxHub dependency. The remote script's contents and any further effects cannot be determined from this chunk.
Piping an HTTPS download directly into bash executes whatever the endpoint currently returns without version pinning or independent integrity verification. A compromised distribution endpoint or altered installer could execute arbitrary code with the agent's local permissions; the PowerShell installation 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 execute third-party installation scripts when the CLI is missing without explicitly obtaining approval for local software installation. Although this is a legitimate dependency setup step, it crosses from remote API operations into local code execution and can modify files accessible to the executing account.
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