Security audit
Security checks for vulnerabilities and agentic risk
The Alchemy queries are appropriately scoped, but setup directs the agent to execute an unverified remote installer without a user approval step.
Review the CLI setup before enabling this skill. Prefer a separately reviewed, version-pinned installation and require approval before running either remote installer. Consider the CLI's broader agent-skill installation behavior and OOMOL's handling of connected credentials. The bundled artifact supports read-only Alchemy use; the remote installer's implementation could not be verified.
The supplied command installs remote software rather than searching or reading Alchemy data. Nothing in the supplied chunk establishes this installer as a supporting dependency for the declared functionality. The downloaded script's contents are unavailable, so its further effects cannot be determined.
The command pipes mutable network content directly into Bash without version pinning or independent integrity verification; the PowerShell alternative uses the same download-and-execute pattern. If the distribution endpoint or release pipeline is compromised, attacker-controlled code could execute with the agent's local privileges, potentially accessing files and credentials; HTTPS alone does not prevent this supply-chain scenario.
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
When the CLI is missing, the skill directs the agent to install software by executing remote scripts without requiring explicit approval or explaining local system changes. This crosses the boundary from reading Alchemy data to modifying the host; the missing-command condition limits exposure but does not establish user authorization.
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