Security audit
Security checks for vulnerabilities and agentic risk
The WebinarJam workflow is coherent, but its automatic setup runs unchecked remote installers without clear approval or disclosure of broader agent changes.
Review the setup before installing. Use a reviewed, fixed CLI version, control its bundled-skill synchronization, and confirm which WebinarJam account and registrant data OOMOL may access. Keep the required confirmation for registrations. The remote installers and hosted connector were not verified; the review concern is uncontrolled setup behavior, not evidence of malicious intent.
The supplied code performs remote installer execution rather than any visible WebinarJam operation. Nothing in the chunk establishes this installation as a supporting dependency for WebinarJam. The downloaded script's contents are not provided, so its further behavior cannot be determined.
Piping a remotely fetched script directly into Bash executes mutable external code without integrity verification or a review opportunity; the PowerShell alternative has the same weakness. A compromised distribution endpoint could execute arbitrary code with the agent's local privileges, although the missing-CLI condition limits when this path is reached and an enforced oo-only tool allowlist could block 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 install software after a missing-command error without first disclosing local system changes or obtaining installation approval. Although prerequisite setup is legitimate and conditional, a request to operate WebinarJam does not necessarily authorize executing an installer with the agent's local 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