Security audit
Security checks for vulnerabilities and agentic risk
The Vitally integration has clear safeguards for data changes, but its setup instructions can trigger an unverified remote installer without separate user approval.
Review and install the CLI yourself before enabling this skill, including its bundled-skill behavior. Understand that OOMOL handles the Vitally connection, and retain the required approvals for data changes. The remote installer contents were unavailable for inspection; this Review verdict concerns setup control, not evidence of malicious intent.
The supplied chunk performs remote script execution and shows no Vitally data operations or connection between the Oomol installer and the declared Vitally functionality. On the supplied evidence, this is an unrelated installation capability rather than an established supporting implementation detail. The downloaded script's contents and further effects are not visible.
Piping an HTTPS response directly into bash executes mutable remote code without a pinned version, independent integrity verification, or an inspection step; the PowerShell alternative has the same trust problem. A compromised distribution endpoint or installer could execute arbitrary code with the invoking user's permissions, including accessing local data and credentials. The legitimate dependency context and missing-CLI condition reduce exposure but do 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 missing-CLI fallback instructs installation through downloaded scripts without explaining that this executes code locally or requiring approval for changes to the host. The conditional fallback limits exposure, but authorization to perform Vitally operations does not necessarily authorize installing software or modifying the local environment.
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