Security audit
Security checks for vulnerabilities and agentic risk
The AppVeyor operations fit the stated purpose, but setup can execute unverified installers and introduce broader agent changes without explicit approval.
Review setup before installing. Install a verified CLI release yourself, explicitly control its agent-skill synchronization, and connect AppVeyor using the narrowest available read permissions. AppVeyor requests pass through OOMOL. The review concern is uncontrolled setup and persistent agent changes; the artifact does not establish malicious intent. Remote installer behavior and server-side credential handling remain unverified.
The supplied command contacts cli.oomol.com, not AppVeyor, and executes the downloaded installer. Nothing in the chunk performs AppVeyor operations or establishes that this installation supports the declared purpose. The downloaded script's contents and further effects are not visible.
The supplied chunk only initiates login; it contains no AppVeyor search or read operation and does not establish that the authentication targets AppVeyor. Authentication could support a larger integration, but no such connection is shown in this chunk.
Piping a mutable HTTPS response directly into bash executes whatever code the installation endpoint supplies with the invoking user's privileges. HTTPS protects transport but does not protect against a compromised publisher or distribution endpoint; the legitimate dependency-installation context does not provide independent integrity verification.
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 setup instructs execution of downloaded shell and PowerShell scripts without an explicit approval or integrity-verification step. This can turn a read-only AppVeyor request into local code execution and system modification; triggering it only when the CLI is missing limits exposure but does not eliminate the risk.
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