Security audit
Security checks for vulnerabilities and agentic risk
The Iru lookups are appropriately scoped, but setup can run unreviewed installation scripts and introduce undisclosed changes to other agent skills.
Review setup before installing. Verify and install a chosen CLI release yourself, require approval for installation changes, and restrict the OOMOL connection to the data you need. To prevent cross-agent skill changes, upstream documents OO_SKILLS_SYNC_DISABLED=1. Remote installer contents and deployed connector behavior remain unverified. [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md)
The supplied command performs remote script execution, which is not represented by the declared Iru data-access purpose. No Iru access or necessary connection between this installer and Iru functionality is shown. The downloaded script's contents and resulting system changes cannot be determined from this chunk.
Piping a remotely retrieved installer directly into bash executes mutable external code with the agent process's local privileges, without integrity verification or an opportunity to review the downloaded artifact. Compromise of the installer distribution could expose local credentials or alter files; the analogous PowerShell command has the same risk, even though both appear only in conditional dependency setup.
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 instructs the agent to install software after a command-not-found error without first obtaining permission for local system changes. A request to read Kandji data does not inherently authorize executing an installer, although limiting setup to a genuine missing dependency reduces exposure.
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