Security audit
Security checks for vulnerabilities and agentic risk
The HR reading workflow is coherent, but its automatic setup can execute unverified downloaded software without a separate approval step.
Review the setup before installing. Install a verified CLI release yourself and require approval before the agent runs downloaded installers. Review the CLI's bundled-skill synchronization and whether your organization permits OOMOL to handle employee data. The remote installers and connector implementation could not be verified; the artifact does not establish malicious intent.
The supplied chunk executes an Oomol CLI installer rather than accessing Sage HR data. No connection between this installer and the declared Sage HR functionality is established, so it cannot be treated as merely a supporting implementation detail. The remote script's contents and any further effects are not visible in the supplied code.
The command pipes a mutable remote script directly into Bash without version pinning or integrity verification; the PowerShell alternative has the same execution pattern. Compromise of the distribution infrastructure could execute attacker-controlled code with the agent process's local permissions, although exploitation requires reaching setup and being permitted to run the installer.
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
On a missing-CLI error, the workflow directs the agent to install software without explicitly obtaining approval for code execution and local system changes. The conditional setup limits exposure, but an ordinary read-only HR request could still trigger an installation the user did not authorize.
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