Security audit
Security checks for vulnerabilities and agentic risk
The Airmeet actions only read data, but setup directs the agent to execute downloaded software without verification or a clear approval step.
Prefer an independently reviewed oo installation, and require approval before running either downloaded installer. Airmeet access uses your OOMOL-connected account, so review its granted permissions. Also review the CLI's automatic skill installation behavior. The bundled instructions were fully inspected, but the external installer contents and exact system changes could not be verified.
The supplied code performs remote script execution rather than searching or reading Airmeet data. Although installation can be a supporting implementation detail, the supplied chunk establishes no connection between this installer and the declared Airmeet functionality. The downloaded script's contents and any further effects are not visible and cannot be determined.
Piping a mutable HTTPS response directly into Bash executes its contents without version pinning, independent integrity verification, or review. A compromised installer host or distribution pipeline could thereby execute attacker-controlled code with the user's privileges; the OOMOL dependency is legitimate context 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 setup instructs the agent to execute downloaded shell or PowerShell code without first obtaining approval for local software installation or explaining its effects. Although this occurs only when the CLI is missing, it expands a read-oriented Airmeet task into arbitrary code execution with the executing user'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