Security audit
Security checks for vulnerabilities and agentic risk
The KnowBe4 reading workflow is coherent, but its setup fallback executes downloaded code without verification or a clear approval step.
Review and approve CLI installation separately, including its automatic agent-skill changes. Use a verified CLI version and a least-privilege KnowBe4 connection, and understand that OOMOL brokers access to the requested data. The remote installers and live connector were not verified; no malicious behavior was established in the supplied artifact.
The supplied command performs remote installer execution, not a KnowBe4 search or read operation. Nothing in the supplied chunk establishes this installer as a necessary supporting dependency for the declared purpose. The downloaded script's contents are unavailable, so its further behavior cannot be determined.
Piping an unpinned remote script directly into bash executes whatever the installation endpoint supplies, without independent integrity verification or review. Compromise of the endpoint or its delivery infrastructure could execute attacker-controlled code with the invoking user's permissions; HTTPS alone does not protect against a compromised publisher.
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 remote shell or PowerShell installers without an explicit user-approval step or warning about arbitrary third-party code execution and system changes. A request to read KnowBe4 data does not inherently authorize software installation; the missing-CLI condition limits exposure but does not establish that authorization.
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