Security audit
Security checks for vulnerabilities and agentic risk
The Aimfox workflow has clear approval controls, but its setup executes remote installers without separate consent or a clear account of lasting changes.
Review and separately approve CLI installation before use. Trusting this integration also means trusting OOMOL with the connected Aimfox account. Check the CLI's automatic skill synchronization before allowing it to modify agent settings; its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md) documents a control to disable startup synchronization. Installer contents and live connector behavior remain unverified.
The supplied chunk runs an installer hosted by Oomol and contains no Aimfox operations or evidence connecting that installation to Aimfox functionality. This is a materially different activity, not an established supporting implementation detail. The downloaded script's contents are unavailable, so its further behavior cannot be determined.
Piping a mutable remote installer directly into bash executes its contents with the invoking user's permissions without prior inspection or independent integrity verification. The OOMOL domain is contextually appropriate and HTTPS protects transport, but a compromised distribution endpoint or malicious installer update could still execute arbitrary code; the PowerShell example has the same weakness.
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 install software by immediately executing downloaded shell or PowerShell code, without requiring user approval for local system changes. Limiting setup to a missing-CLI error reduces exposure, but the write and destructive-action confirmations only cover Aimfox operations and do not explicitly protect this installation path.
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