Security audit
Security checks for vulnerabilities and agentic risk
The Dropbox workflow has clear safeguards, but setup directs the agent to execute unverified remote installation code without separate approval.
Review and approve CLI installation separately using a fixed, verified release. Check its agent-skill installation behavior before first use. Connecting Dropbox entrusts OOMOL with account access, and downloads enter transit storage with unspecified retention. Keep the documented approvals for writes and deletions. The external installer and connector internals remain unverified.
The supplied command installs remote software rather than performing any visible Dropbox operation. Although installation can be a supporting implementation detail, the supplied chunk establishes no relationship between this installer and the declared Dropbox functionality. The remote script's contents and any further behavior cannot be determined from this chunk.
Piping a mutable HTTPS response directly into bash executes remote code without checking a pinned version, signature, or trusted checksum; the PowerShell alternative has the same issue. Although the endpoint belongs to the documented CLI provider, compromise of its distribution infrastructure could yield arbitrary code execution and access to local files or credentials.
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 setup instructs the agent to execute remote shell or PowerShell scripts without first obtaining approval for local installation or explaining its system-level effects. Limiting this to a missing-CLI error reduces exposure, but a routine Dropbox request can still trigger execution of installer-controlled code with the invoking user's privileges.
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