Security audit
Security checks for vulnerabilities and agentic risk
The currency-data features fit their purpose, but setup can execute unverified remote installers and introduce broader agent changes without clear user approval.
Review the setup behavior before installing. Install a reviewed, integrity-verified CLI release separately and require approval for local changes. Review or disable its automatic skill synchronization, and connect only the intended currencyapi account. The remote installer contents and hosted credential handling remain unverified; the artifacts do not establish malicious intent.
The missing-CLI fallback expands a read-oriented task into executing remote installation code locally without an explicit approval or integrity-verification step. OOMOL is actually disclosed as the integration provider, so this is not evidence of a concealed third party or malicious purpose; the vulnerability is the unsafe installation workflow, overlapping with SQP-2 and SC2.
The supplied chunk performs only a login operation; it does not search or read currencyapi data. Authentication could support an API integration, but nothing in this chunk establishes that this login is for currencyapi or supports the declared functionality.
Piping an HTTPS response directly into bash executes mutable remote content without a pinned version, integrity verification, or review. If the installer hosting or distribution pipeline is compromised, the command can run attacker-controlled code with the invoking user's privileges; the legitimate provider domain and conditional setup context 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 setup instructions direct execution of downloaded shell and PowerShell scripts without first describing local changes or obtaining explicit installation approval. Restricting this behavior to a missing dependency reduces exposure, but a currency-data request still does not inherently authorize running an installer with the user's local privileges.
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