Security audit
Security checks for vulnerabilities and agentic risk
The bookmark operations have clear safeguards, but automatic CLI setup executes unverified downloaded code and needs review.
Review and explicitly approve CLI installation before allowing automatic setup, including any installation or updating of other agent skills. Connecting Raindrop entrusts OOMOL with account access. Bookmark changes and deletions have explicit confirmation safeguards. The Review verdict concerns setup behavior; the inspected artifact does not establish malicious intent, and remote installer contents remain unverified.
The supplied chunk performs remote script execution rather than Raindrop.io data operations. Nothing in the chunk establishes the Oomol installer as a supporting dependency for the declared purpose. The downloaded script's contents are not supplied, so its further behavior cannot be determined.
The command streams an unpinned remote script directly into Bash, granting whatever code the endpoint returns execution privileges on the local machine. HTTPS protects transport but does not establish that the script is safe or protect against compromise of the publisher. This is the same underlying installation weakness as SQP-2, not 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
The setup instructions pipe remotely retrieved shell and PowerShell scripts directly into interpreters without verifying their integrity or obtaining installation-specific approval. If the distribution endpoint or its publishing infrastructure is compromised, following these instructions could execute attacker-controlled code with the invoking user's privileges. The missing-CLI condition reduces exposure but does not remove this supply-chain risk.
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