Security audit
Security checks for vulnerabilities and agentic risk
The Dropbox Sign reads fit the stated purpose, but setup can execute unchecked installation code and introduce undisclosed changes to agent skills.
Review and approve CLI installation separately, verify a fixed release, and consider disabling automatic skill synchronization with OO_SKILLS_SYNC_DISABLED=1. Connect only the account needed for your reads and understand that OOMOL brokers access to its private records. The external installer and server-side connector implementation were not verified.
The supplied command performs remote code execution for an installer, not Dropbox Sign searching or reading. Nothing in the supplied chunk establishes that this installation is a supporting dependency for Dropbox Sign, and the downloaded script's further behavior cannot be determined from this code.
The command pipes a mutable remote script directly into Bash without pinning or verifying its contents; the PowerShell alternative has the same execution pattern. If the distribution endpoint or publishing pipeline is compromised, attacker-controlled code could run with the agent's local privileges and access files or credentials. HTTPS and the legitimate CLI dependency reduce some concerns but do not establish script integrity.
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 install software when the CLI is missing without first explaining local changes or obtaining installation-specific approval. A request to read Dropbox Sign data does not itself authorize executing an installer on the user's machine, although the missing-command prerequisite limits when this behavior occurs.
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