Security audit
Security checks for vulnerabilities and agentic risk
The ERP controls are clear, but its required CLI can silently install and update skills across agent environments without disclosure here.
Review the CLI's installation and skill-management behavior before proceeding. Install a verified release yourself and consider setting OO_SKILLS_SYNC_DISABLED=1 before invoking it to prevent automatic skill synchronization, as documented in the [CLI reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Keep ERP changes subject to the skill's approval requirements and share only necessary tracking fields. The remote installers and hosted connector implementation remain unverified; no malicious behavior was established.
The visible code functions as a remote installer, not a Jushuitan ERP interface. Installation could be a supporting implementation detail, but the supplied chunk establishes no connection between this installer and the declared ERP functionality. The downloaded script is not provided, so its further behavior cannot be determined.
The setup instructions pipe a mutable remote script directly into Bash, and the Windows alternative similarly executes downloaded content immediately. If the distribution endpoint or release pipeline is compromised, attacker-controlled code runs with the user's privileges and could access local credentials or alter files. The missing-CLI condition limits exposure, but HTTPS alone does not establish the integrity of the delivered installer.
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
This is an instruction to use Kuaidi100 for tracking requests, not merely a tool listing. Although it requires checking service availability and connection status, it does not disclose that tracking numbers and any other required query data will be transmitted outside the Jushuitan ERP workflow.
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