Security audit
Security checks for vulnerabilities and agentic risk
The apaleo actions require appropriate user approval, but first-time setup directs execution of unverified downloaded code without a separate approval step.
Review setup before enabling this skill. Install a verified CLI release yourself, review its management of other agent skills, and prevent automatic remote-installer execution. OOMOL mediates account access and receives requested operation payloads. Continue requiring approval for exact write and deletion targets; the external installers and hosted connector were not verified.
The supplied command performs remote software installation rather than any visible apaleo operation. Although installing a CLI could be a supporting implementation detail, the supplied content establishes no relationship between this installer and the declared apaleo functionality. The downloaded script's contents and subsequent effects are not available for assessment.
Piping a mutable remote script directly into bash executes its contents with the agent process's local permissions, without version pinning or integrity verification. Compromise of the installer distribution could therefore expose accessible files and credentials or modify the environment; HTTPS and the legitimate CLI dependency 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 fallback directs the agent to execute downloaded shell or PowerShell code without first obtaining explicit approval for local installation and its system changes. The missing-CLI condition limits exposure, but an apaleo request does not itself authorize arbitrary installer execution on the user's machine.
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