Security audit
Security checks for vulnerabilities and agentic risk
The Docsumo workflow is clearly scoped, but setup can execute downloaded software and introduce additional agent instructions without separate approval.
Review the setup before installing. Install a reviewed, version-pinned CLI yourself and disable automatic skill synchronization if you want only this Docsumo integration. Connect an account whose document data you intend the agent and OOMOL to access, and confirm uploads. The downloaded installers and hosted implementation remain unverified; the artifacts do not establish malicious intent.
The supplied code performs remote software installation rather than any visible Docsumo operation. Nothing in the chunk establishes that the Oomol installer is a necessary supporting dependency. The downloaded script's contents are not supplied, so its additional behavior cannot be determined.
Piping a network response directly into bash executes whatever script the endpoint supplies with the agent process's privileges. HTTPS protects transport but does not establish immutable installer integrity, so a compromised distribution endpoint could expose local files and credentials or modify the host; the missing-CLI prerequisite reduces exposure but does not eliminate it.
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 instructs the agent to execute remotely downloaded shell or PowerShell code without a separate approval step, integrity verification, or review. Although limited to a missing-CLI error, this can turn an ordinary Docsumo request into host-level code execution if the installer distribution is compromised; it overlaps with SC2 rather than representing an independent exploit.
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