Security audit
Security checks for vulnerabilities and agentic risk
The Claid AI workflow is coherent, but setup can execute unverified remote code without clear user approval.
Review or independently install the CLI before allowing setup to run, and check its managed-skill synchronization settings before first use. Understand that OOMOL mediates access to your Claid account. Image edits require confirmation, but local installation changes lack equivalent controls. The bundled instructions were fully inspected; remote installer, CLI, and server behavior remain unverified.
The supplied chunk installs software from Oomol rather than performing Claid AI operations. Nothing provided establishes this installation as a supporting dependency for Claid AI. The downloaded script's contents are not shown, so its further behavior cannot be assessed.
Piping the HTTPS response directly into Bash executes mutable remote content without first verifying a pinned release, signature, or trusted checksum; the PowerShell alternative has the same problem. If the distribution endpoint or delivery chain is compromised, the script can execute with the invoking user's permissions and potentially access local files and credentials. The installer is relevant to the documented workflow, but that relevance does not establish its 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
The setup instructions direct the agent to install software after a missing-command error without requiring user approval or explaining that downloaded code will execute and may change the local environment. Restricting setup to an actual dependency failure reduces exposure, but the confirmation requirements for Claid write actions do not cover these local installation changes.
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