Security audit
Security checks for vulnerabilities and agentic risk
The Demio workflow is well scoped, but its setup fallback executes unverified remote installers without clearly obtaining approval for local changes.
Review the setup path before installing. Prefer an independently verified CLI release and explicitly approve local changes. Check and control the CLI's broader skill synchronization, documented in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). OOMOL will mediate Demio access and related attendee data. The bundled instructions were fully inspected, but the external installers and server behavior remain unverified.
The supplied code performs remote installer execution rather than any visible Demio operation. Although installing a CLI could be a supporting implementation detail, this chunk provides no evidence linking the Oomol installer to the declared Demio functionality. The downloaded script's additional behavior cannot be determined from the supplied code.
Piping a live HTTPS response directly into bash executes remote code without version pinning or independent integrity verification. Compromise of the distribution endpoint or its supply chain could yield arbitrary code execution with the agent's privileges; the legitimate CLI dependency and missing-command condition narrow exposure but do not eliminate it.
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 a remote installer without first explaining its system-level effects or requesting approval. Although conditional setup is relevant to Demio access, authorization to operate Demio does not necessarily authorize installing arbitrary code on the host; execution could modify files or access data with the agent's privileges.
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