Security audit
Security checks for vulnerabilities and agentic risk
This Drive skill requires review because its setup can run an unverified online installer without first requesting your approval.
Review and approve the CLI installation separately, preferably using a pinned release with verified integrity. Check its automatic skill synchronization settings before allowing persistent changes to other agents. Connect only the Drive access you need and retain the stated approval steps for edits, sharing, and deletion. The remote installers and hosted connector implementation could not be inspected; no malicious behavior was established.
The only observable behavior is remote installer execution, rather than Google Drive management. Although installing a dependency can be a supporting implementation detail, the supplied chunk establishes no connection between this installer and the declared functionality. The downloaded script's contents and any further effects cannot be determined from this chunk.
The command pipes a mutable HTTPS response directly into bash without verifying a pinned artifact, signature, or independently authenticated checksum. HTTPS protects transport but does not prevent a compromised distribution endpoint from delivering malicious code that could access local files and credentials; this is the same underlying installation risk identified by SQP-2.
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 execution of remotely retrieved shell or PowerShell code without an explicit installation approval step or independent integrity verification. If the installer distribution is compromised, this can execute attacker-controlled code with the invoking user's privileges; limiting installation to a missing-CLI error reduces exposure but does not eliminate it.
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