Security audit
Security checks for vulnerabilities and agentic risk
The ablefy reading workflow is coherent, but setup directs the agent to execute downloaded software without first obtaining your approval.
Review and approve CLI installation separately, using a verified release. Connecting ablefy entrusts OOMOL with access to that account. Check whether the chosen CLI release installs additional agent skills; upstream documents OO_SKILLS_SYNC_DISABLED=1 to disable startup skill synchronization in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). The remote installer's full effects remain unverified.
The supplied code runs a remote Oomol installer rather than searching or reading ablefy data. Nothing in the chunk establishes that this installation supports the declared ablefy functionality, and the description does not disclose software installation or remote shell execution.
The command streams a remotely retrieved script directly into bash without pinning an artifact or verifying its integrity before execution; the PowerShell alternative has the same trust issue. HTTPS protects transport but does not prevent a compromised distribution server or malicious installer update from executing code with the agent's privileges, potentially accessing local files and credentials.
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 missing-CLI fallback instructs the agent to install software by executing remote scripts without first obtaining explicit approval for local system changes. Although this path is conditional and supports a legitimate dependency, an ablefy data-reading request does not by itself authorize arbitrary installer execution 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