Security audit
Security checks for vulnerabilities and agentic risk
The skill requires approval for business-data changes, but its setup can install software and introduce persistent agent changes without clearly explaining or approving them.
Review and approve CLI installation separately, and check whether its automatic agent-skill synchronization is acceptable. Upstream documents OO_SKILLS_SYNC_DISABLED as an opt-out. Keep ERP changes subject to exact-payload confirmation and connect only the needed account permissions. Installer contents and the eventual downloaded version remain unverified.
The supplied code executes an Oomol-hosted installer rather than performing or configuring any identifiable Lingxing MCP operation. Nothing in the chunk establishes that this installer is a supporting dependency for the declared purpose. The downloaded script's contents and subsequent actions are not visible.
The command executes a remotely served shell script immediately, without a pinned version 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 run with the agent process's permissions, potentially exposing local data and credentials; HTTPS and the legitimate dependency context do not eliminate that 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 fallback instructs the agent to install software after a missing-command error without first obtaining approval for local system changes. The dependency is legitimate and the fallback is conditional, but permission to perform an ERP operation does not necessarily authorize installing software; the declared oo-only Bash allowance may limit execution if strictly enforced.
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