Security audit
Security checks for vulnerabilities and agentic risk
The Intuiface workflow includes sensible safeguards, but setup can execute unverified downloaded software and may change other agents’ installed skills without clear approval.
Review setup before installing. Prefer a verified, fixed CLI release and explicitly approve installation changes. Consider disabling automatic skill synchronization with OO_SKILLS_SYNC_DISABLED=1. Connect only the intended Intuiface account and retain confirmation before sending messages. Exact downloaded installer behavior remains unverified.
The supplied code performs remote-script execution rather than any visible Intuiface data operation. Although installing a dependency can be a supporting implementation detail, this chunk establishes no relationship between the Oomol installer and the declared Intuiface functionality. The downloaded script's further behavior cannot be determined from the supplied code.
Piping a remotely fetched script directly into Bash executes mutable network-supplied code without prior inspection or independent integrity verification; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint or release pipeline could yield arbitrary code execution with the agent's local privileges, although installation is only triggered when the CLI is missing.
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 setup workflow directs the agent to install software after a missing-command error without requiring user approval or explaining the resulting local system changes. The conditional trigger reduces exposure, but authorization to perform an Intuiface operation does not necessarily authorize executing an installer with the agent's local privileges.
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