Security audit
Security checks for vulnerabilities and agentic risk
The Mendeley workflow is appropriately scoped, but setup can execute unverified downloaded software without a separate approval step.
Review setup before installing. Prefer a separately approved, verified CLI installation and check its automatic agent-skill synchronization settings. OOMOL mediates access to your connected Mendeley account. Library changes require confirmation, but the remote installer's contents and exact effects could not be verified.
The visible code's sole action is executing an Oomol-hosted installer. Nothing in the supplied chunk establishes this as a supporting dependency for Mendeley functionality. Its installation purpose and accessed resource therefore materially differ from the declaration. The remote script's contents and any additional effects cannot be determined from this chunk.
Piping a remote response directly into Bash executes mutable third-party code without checking its integrity or reviewing it; the PowerShell alternative has the same issue. If the distribution endpoint or release pipeline is compromised, the installer can run arbitrary code with the invoking user's permissions, potentially accessing local files and credentials. The legitimate OOMOL dependency and conditional setup reduce exposure frequency but do not remove this supply-chain risk.
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 the agent to execute downloaded installation scripts without explicitly seeking approval for local system changes or explaining the trust involved. Although installation is a legitimate prerequisite and only occurs when the CLI is missing, approval rules for Mendeley writes do not clearly cover this separate host-level operation.
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