Security audit
Security checks for vulnerabilities and agentic risk
The CoinGecko workflow fits its purpose, but setup can execute unverified remote code and introduce broader changes to agent skills without explicit approval.
Review setup before installing. Provision a verified CLI version yourself and require approval before remote installers run. Consider disabling the CLI's automatic skill synchronization. CoinGecko requests pass through OOMOL and may consume credits. The remote installer and server implementation were not verified.
The supplied code executes an external installer rather than performing the declared CoinGecko operations. Although dependency installation can be a supporting implementation detail, this chunk provides no evidence connecting the Oomol installer to CoinGecko functionality. The downloaded script's contents and any further effects are not available for assessment.
The supplied code contains only an authentication command. It shows neither CoinGecko data access nor evidence that this login is a supporting step for CoinGecko operations. Its observable purpose therefore differs materially from the declared data-search and reading purpose.
The command streams a mutable remote script directly into Bash without a pinned version, independently verified integrity, or review before execution; the PowerShell alternative has the same issue. If the distribution endpoint or its supply chain is compromised, the installer can execute arbitrary commands with the invoking user's privileges, potentially exposing local credentials and files. Its legitimate setup purpose and HTTPS transport reduce suspicion of deliberate malice but do not remove this execution 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 install software without explicitly warning about local system changes or requesting approval. Although installation supports the stated workflow and is conditional, a read-only data request does not itself authorize downloading and executing an installer; actual execution also depends on the host's tool restrictions.
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