Security audit
Security checks for vulnerabilities and agentic risk
The FullEnrich lookups fit the stated purpose, but automatic setup can run unchecked downloaded code and change other agent skills without clear user approval.
Review the setup behavior before installing. Arrange a separately approved, verified CLI installation and consider disabling its automatic skill synchronization with OO_SKILLS_SYNC_DISABLED. Understand that OOMOL mediates FullEnrich requests and account access. The concern is the automatic setup and broader lasting effects; the artifacts do not establish deception or data theft. Remote installer contents could not be inspected.
The supplied command performs remote script execution for an Oomol CLI installer, with no visible FullEnrich interaction. This is a materially different operation from the declared data-access purpose, and the supplied code provides no evidence that the installer is a supporting dependency for FullEnrich. The remote script's contents and further effects are not available for assessment.
Piping a mutable HTTPS response directly into bash executes remote code without an independently verified signature, digest, or pinned release. Compromise of the installer distribution path could therefore execute attacker-controlled code with the agent's local permissions; HTTPS and the legitimate dependency context do not eliminate this supply-chain risk.
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 a downloaded installer without first obtaining approval for local software installation or explaining its effects. Although conditional and relevant to setup, this crosses from reading service data into local code execution with the executing user's permissions.
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