Security audit
Security checks for vulnerabilities and agentic risk
The Document360 reading functions fit the stated purpose, but automatic setup can execute unverified remote code and introduce persistent agent changes without clear user approval.
Review before installing. Use a separately reviewed, version-controlled CLI installation and require approval for setup changes. Review or disable managed-skill synchronization using the documented OO_SKILLS_SYNC_DISABLED control. OOMOL will mediate access to your connected Document360 account. No malicious behavior was established, but the remote installer and exact installed CLI behavior were not verified.
The supplied chunk performs remote code installation/execution rather than the declared Document360 data operations. Although installation can support a skill, the supplied content establishes no connection between this installer and Document360. The downloaded script's contents and additional effects cannot be determined from this chunk.
The command streams a mutable remote script directly into Bash without pinning or independently verifying the downloaded artifact; the PowerShell alternative has the same execution pattern. If the distribution endpoint or release infrastructure is compromised, attacker-controlled code could execute with the invoking user's privileges, exposing local files and credentials. HTTPS and the conditional setup trigger reduce some exposure but do not establish artifact integrity; this overlaps with SQP-2 rather than representing a separate exploit chain.
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
A missing CLI triggers instructions to install software without requiring approval or explaining the resulting local changes, expanding a read-only data request into a host-modifying operation. The error-only trigger limits exposure, and a strictly enforced Bash(oo *) allowlist could block these commands, but neither makes the prescribed setup behavior safe when installation is permitted.
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