Security audit
Security checks for vulnerabilities and agentic risk
The Qdrant operations have clear approval controls, but automatic software installation and undisclosed changes to agent skills warrant review.
Review and approve CLI installation separately, using a fixed release with verified integrity. Check or disable its automatic agent-skill synchronization before use. OOMOL mediates access to your Qdrant account, so use narrowly scoped credentials and retain the documented approval checks for database changes. The remote installer and resulting CLI release were not verified; no malicious behavior was established.
The supplied code executes an external installer rather than performing Qdrant Cloud operations. Nothing in the chunk establishes that this installer is a supporting dependency for the declared purpose. The downloaded script's contents and any further effects are not available for assessment.
Piping a mutable HTTPS download directly into bash executes whatever the installer endpoint returns, without a pinned version or independent integrity verification. HTTPS protects transport but does not prevent a compromised publisher or hosting service from serving malicious code that could access local files and credentials. The legitimate dependency-installation context explains the command but does not eliminate 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 shell or PowerShell code without reviewing it, verifying a pinned artifact, or obtaining explicit approval for local software installation. Restricting this to a missing-CLI error reduces exposure, but a compromised installer or distribution service could still execute arbitrary code with the invoking account's permissions; the missing warning is secondary to that execution 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
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## Resources
- Qdrant Cloud homepage: https://qdrant.tech/cloud/
- API documentation: https://api.qdrant.tech/