Security audit
Security checks for vulnerabilities and agentic risk
The Tushare functionality is coherent, but setup can execute unverified downloaded code and introduce broader agent changes without clear user approval.
Review setup before installing. Prefer a separately reviewed CLI installation and control its automatic skill synchronization. Connecting Tushare entrusts its API key and queries to OOMOL and may incur charges. No malicious behavior was established, but the remote installers and server implementation were not verified.
The supplied command performs remote installer execution rather than searching or reading Tushare data. Nothing in the supplied code establishes that this installation supports the declared Tushare functionality. The downloaded script's contents and further effects cannot be determined from this chunk.
The supplied chunk performs only an authentication command and shows no Tushare search or data-reading behavior. Authentication could be a supporting implementation detail if tied to Tushare, but no such connection is established here; the visible behavior instead targets the oo CLI.
Piping a mutable remote installer directly into bash executes its contents without an opportunity for inspection or independent integrity verification. If the installer distribution endpoint is compromised, attacker-controlled code could access local files and credentials or modify the environment; 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
The fallback workflow instructs the agent to execute downloaded shell or PowerShell code without first explaining the local changes or obtaining explicit installation approval. Although installation supports the stated task and only occurs when the CLI is missing, it crosses from reading financial data into executing code with the invoking user's 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