Security audit
Security checks for vulnerabilities and agentic risk
The FinChina workflow is coherent, but its setup executes unverified remote software and leaves persistent changes to agent skills insufficiently disclosed.
Review and install a verified CLI release yourself before enabling this skill. Consider disabling startup skill synchronization with OO_SKILLS_SYNC_DISABLED=1, as documented in the [CLI reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Queries use your connected account through OOMOL and may consume credits. The exact remote installers and connector implementation were not verified.
The supplied code executes an installer from an Oomol domain rather than searching or reading FinChina data. No connection establishing this installation as a supporting dependency for the declared purpose is shown. The downloaded script is not supplied, so its further behavior cannot be assessed.
The command pipes an unpinned remote script directly into bash, allowing its contents to execute without prior inspection or integrity verification. HTTPS protects transport but does not protect against a compromised distribution endpoint or malicious upstream change; the missing-CLI condition limits exposure but not the resulting execution privileges.
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 directs execution of remote shell and PowerShell installers without requiring review, integrity verification, or explicit approval for local software installation. Although conditional and legitimately related to setup, this can turn a missing dependency into arbitrary code execution with the invoking user's privileges if the installer source is compromised; this overlaps with SC2 rather than representing a separate exploit.
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