Security audit
Security checks for vulnerabilities and agentic risk
The ProcessPlan actions have sensible controls, but setup can execute unverified remote software with broader effects than the skill explains.
Review and approve CLI setup separately before letting the agent install it. Use a vetted release and inspect its installer. Consider disabling automatic skill synchronization using the publisher's documented OO_SKILLS_SYNC_DISABLED setting. OOMOL will mediate your ProcessPlan access and data. No malicious behavior was established, but the remote installer could not be inspected.
The supplied code installs or runs external software rather than performing any visible ProcessPlan operation. No connection is shown that would establish this installer as a supporting implementation detail for the declared purpose. The downloaded script's contents are not supplied, so its further behavior cannot be determined.
The curl-to-bash pipeline executes the current contents of a remote installer without a pinned version or independent integrity verification. HTTPS protects transport but does not protect against a compromised publishing account or installer host, which could deliver code capable of accessing local files and credentials; this is the same underlying installation risk flagged by SQP-2.
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 execute downloaded shell or PowerShell code without explaining that this grants remote code the local user's privileges or requiring installation approval. Although limited to first-time setup, a missing dependency can trigger a transition from a ProcessPlan task to arbitrary local code execution if the installer delivery is compromised.
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