Security audit
Security checks for vulnerabilities and agentic risk
The Celigo features fit the stated purpose, but fallback setup directs the agent to execute unverified downloaded code without clear user approval.
Review and install the CLI separately using a verified release before enabling this skill, and require approval for installation changes. Celigo access is mediated by OOMOL, so consider the connected account's permissions and data sensitivity. The concern is uncontrolled setup execution; the artifacts do not establish malicious intent.
The supplied code performs remote script execution rather than searching or reading Celigo data. Nothing in the chunk establishes that this installation is a supporting dependency for Celigo access. The downloaded script's contents are unavailable, so its further behavior cannot be determined.
Piping a remotely fetched script directly into Bash executes mutable network-delivered code without a pinned version or independent integrity verification; the PowerShell fallback has the same weakness. Compromise of the distribution endpoint could execute attacker-controlled code with the invoking user's privileges, potentially exposing local files and credentials; HTTPS and the legitimate setup purpose 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 instructs the agent to install software without explicitly obtaining approval for executing downloaded code or changing the local environment. Restricting this to a command-not-found error reduces exposure, but a read-only Celigo request does not itself authorize software installation; the declared Bash allowlist may constrain execution but does not make the guidance safe.
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