Security audit
Security checks for vulnerabilities and agentic risk
The HasData workflow is coherent, but its setup can execute unchecked downloaded code and change other agent skills without clear user control.
Review before installing. Arrange CLI setup separately using a verified release and approve its local changes. Check or disable automatic synchronization of additional agent skills. OOMOL mediates HasData requests and account access. The entire bundled skill was inspected; the scanner's reference gaps were resolved, but downloaded installer behavior remains unverified. No artifact-backed evidence establishes malicious intent.
The supplied command executes an external installer, with no visible HasData search or read operation or demonstrated connection to HasData. This introduces remote code execution and an apparent installation capability not represented by the declared purpose. The fetched script is not supplied, so its further actions cannot be assessed.
The supplied chunk only invokes a CLI login command; it contains no HasData search or read operation and does not establish that oo authenticates to HasData. Although authentication could be a supporting implementation detail if that connection were demonstrated, the visible behavior does not substantiate the declared purpose.
The command pipes a mutable HTTPS response directly into bash without a pinned version, integrity verification, or review. Compromise of the installer host or delivery infrastructure could therefore produce arbitrary code execution with the agent process's permissions; the conditional fallback limits exposure but does 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 missing-CLI fallback directs installation through downloaded shell or PowerShell code without requiring explicit user approval or explaining local system changes. Although conditional setup is legitimate, executing a third-party installer can modify the environment and access files or credentials available to the executing account.
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