Security audit
Security checks for vulnerabilities and agentic risk
The currency lookups are appropriately scoped, but setup can execute an unverified remote installer and introduce persistent changes to other agent skills without clear user control.
Review and install oo yourself before enabling this skill, and require approval before the agent runs either installer. Consider whether you accept OOMOL handling the connection and the CLI modifying other agent skills. Upstream documents OO_SKILLS_SYNC_DISABLED as a way to disable startup skill synchronization in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). The bundled instructions were fully inspected; the remote installers and hosted implementation remain unverified. No artifact-backed malicious intent was found.
The supplied command invokes a remote installer rather than searching or reading CurrencyBeacon data. Nothing in the chunk establishes this installer as a supporting dependency for the declared purpose. The downloaded script's contents are not supplied, so its further behavior cannot be determined.
The supplied code performs only authentication, not CurrencyBeacon searching or reading. Authentication can be a supporting implementation detail, but this chunk provides no evidence connecting the login to CurrencyBeacon or implementing the declared data-access purpose.
The command pipes a remotely retrieved, mutable script directly into Bash without an independent integrity check or review; the PowerShell alternative uses the same download-and-execute pattern. Although installation serves a legitimate dependency need, compromise of the distribution endpoint could execute attacker-controlled code with the agent process's local permissions.
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
A missing CLI triggers instructions to install software without first explaining the system changes or obtaining approval, expanding a data-reading request into local code execution. The missing-command prerequisite limits exposure, and enforced Bash(oo *) permissions could block these installer commands, but neither constitutes user consent to installation.
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