Security audit
Security checks for vulnerabilities and agentic risk
Recruitee actions have clear approval controls, but setup executes unverified downloads and may change other installed agent skills without sufficient disclosure.
Review and install a verified CLI release separately before using this skill. Consider disabling startup skill synchronization with OO_SKILLS_SYNC_DISABLED=1, as documented in the [CLI reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Confirm that OOMOL may process your recruitment data and retain the required approval controls for changes. The bundled instructions were fully inspected, but the downloaded installer and hosted connector implementation were not verified.
The supplied chunk installs software from an external domain rather than performing Recruitee operations. Although installation can be a supporting implementation detail, nothing in the supplied content establishes this installer's relevance to the declared purpose. The downloaded script is not provided, so its further behavior cannot be assessed.
The curl-to-bash command immediately executes mutable remote content without pinning a version or verifying its integrity. HTTPS protects transport but does not prevent a compromised publisher or distribution endpoint from supplying malicious code; the missing-CLI condition reduces exposure but not the consequences.
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 setup instructions direct the agent to execute downloaded shell or PowerShell code without an explicit approval gate or integrity verification. Although setup is conditional and the URLs belong to the CLI provider, a compromised distribution endpoint could execute arbitrary code with the invoking 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