Security audit
Security checks for vulnerabilities and agentic risk
The document features are appropriately scoped, but setup directs the agent to run unverified downloaded software without separate approval.
Review the setup before installing. Use a verified CLI release and require approval for local installation. Upstream documents OO_SKILLS_SYNC_DISABLED=1 to prevent automatic skill synchronization. OOMOL handles the connected account and document requests, so use the intended account and review each document change or deletion. The remote installers were unavailable for inspection; this review does not establish malicious behavior.
The command executes an Oomol-hosted installation script, which is not disclosed in the description and has no demonstrated connection to DocuGenerate. Although installation can be a supporting implementation detail, the supplied chunk establishes no such relationship. The remote script's contents and any additional effects cannot be determined from this snippet.
The command executes a mutable remote script immediately, without a pinned version or independently verified integrity; the Windows fallback uses the same download-and-execute approach. Compromise of the installer hosting or distribution pipeline could execute arbitrary code with the invoking user's permissions, exposing local files and credentials. The legitimate dependency and conditional setup reduce exposure but do not remove this supply-chain risk.
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 locally without explicitly requesting approval or explaining the system changes. Although limited to a missing-CLI error, this crosses from remote document operations into local code execution, while the skill's confirmation requirements only cover DocuGenerate writes and deletions.
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