Security audit
Security checks for vulnerabilities and agentic risk
The HR lookups fit the stated purpose, but fallback setup runs unverified installer code without a clear approval step and may change other installed agent skills.
Review and approve CLI installation separately before allowing the missing-CLI fallback. Prefer a pinned, verified release, and check or disable automatic synchronization of other agent skills. Confirm that OOMOL may access the requested HR records and limit the connected account accordingly. No malicious behavior was established, but the external installer and hosted connector were not verified.
The supplied chunk contains no Breezy HR access or data-reading functionality. Instead, it executes a remote installer whose connection to the declared purpose is not established. The downloaded script's contents are not provided, so its further behavior cannot be determined.
The curl-to-bash pipeline immediately executes whatever script the remote endpoint supplies, without version pinning or an independent integrity check. HTTPS reduces transport tampering but does not protect against a compromised distribution service; execution could compromise local files and credentials with the agent's operating-system permissions.
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 execute downloaded shell or PowerShell code without first explaining the local execution risk or obtaining installation approval. Although limited to a missing-CLI error, this expands a read-only HR request into local software installation, potentially executing attacker-controlled code if the distribution endpoint is compromised.
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