Security audit
Security checks for vulnerabilities and agentic risk
The WorkOS workflow has clear safeguards, but automatic setup can execute unverified installers and make broader agent changes without clear approval.
Review this skill's setup before enabling it. Install a verified CLI release separately, approve its local changes, and check or disable automatic skill synchronization using the [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Connecting WorkOS entrusts OOMOL with access to the selected account. Keep the skill's explicit approval requirements for account and membership changes. Remote installer contents and hosted behavior were not verified.
The supplied command executes an installer hosted at cli.oomol.com and contains no WorkOS operations or demonstrated WorkOS integration. Installing this unrelated CLI is materially different from the declared purpose, not an established supporting implementation detail. The downloaded script's contents and further effects are not available in the supplied chunk.
Piping an unpinned remote script directly into bash executes its contents without prior inspection or independent integrity verification. Compromise of the script distribution infrastructure could therefore yield arbitrary code execution with the user's privileges; the legitimate connector setup context explains the download but does not remove 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 directs the agent to install software by immediately executing downloaded code, without first obtaining approval for local system changes. Although conditional setup reduces exposure, a request to operate WorkOS does not necessarily authorize installation, and the scripts execute with the invoking user's permissions.
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