Security audit
Security checks for vulnerabilities and agentic risk
The Elevio features are appropriately scoped, but setup directs the agent to run unverified downloaded software without a clear approval step.
Review the CLI installation before enabling this skill. Prefer a verified, fixed release installed with your approval, and check whether it installs or updates other agent skills. Elevio requests use your OOMOL-connected account. The full bundled artifact was inspected, but the remote installers and hosted service implementation remain unverified; no malicious behavior was established.
The supplied chunk performs remote script execution rather than searching or reading Elevio data. Nothing in the supplied content establishes this Oomol installer as a supporting dependency for Elevio access. The downloaded script's contents are not provided, so its further actions cannot be determined.
Piping the HTTPS response directly into bash executes mutable remote content without verifying its integrity or reviewing it first. HTTPS protects transport but does not protect against compromise of the distribution endpoint, which could lead to credential theft or host modification under the executing account. This is the same underlying installation risk highlighted by 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 fallback directs an agent to execute downloaded shell or PowerShell code without explicit approval or integrity verification. A request to read Elevio data does not inherently authorize installing software on the host, and a compromised installation endpoint could execute arbitrary code with the agent process's privileges. The missing-CLI condition limits exposure but does not make this installation safe.
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