Security audit
Security checks for vulnerabilities and agentic risk
The Lever integration fits its purpose, but setup can execute unverified remote code and introduce broader agent changes without clear approval.
Review the CLI installation separately before allowing automatic setup, and approve a specific verified release. Decide whether you want additional skills installed across your agents; the CLI documents OO_SKILLS_SYNC_DISABLED to suppress startup synchronization in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Connect only the intended Lever account and confirm note-writing payloads. Installer contents and hosted connector behavior remain outside the inspected artifact; no malicious behavior was established.
The supplied chunk performs remote installer execution rather than interacting with Lever. Although installation can be a supporting implementation detail, the provided content establishes no relationship between this installer and the declared Lever functionality. The remote script's contents and any further effects cannot be determined from this chunk.
Piping a mutable remote installer directly into bash executes its contents with the agent's local privileges without integrity verification or review. HTTPS protects transport but does not prevent malicious changes following compromise of the distribution service; the conditional setup trigger reduces exposure frequency, not the consequences of execution.
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 missing-CLI fallback directs the agent to execute remote installation scripts without requiring explicit approval for local code execution and system changes. Although dependency setup is relevant to the skill, authorization to access Lever does not necessarily authorize installing software; the write-confirmation rules only explicitly cover Lever state changes.
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