Security audit
Security checks for vulnerabilities and agentic risk
The ERP workflow is coherent, but setup directs the agent to execute unverified downloaded code without a separate approval step.
Before use, install and verify a fixed CLI release yourself and require approval for setup changes. Review or disable its automatic agent-skill synchronization. Connect only the ERP account you intend OOMOL to access, and retain confirmation for writes. The bundled instructions were fully inspected; downloaded installers and hosted connector behavior remain unverified.
The visible behavior is remote software installation rather than ERP data access or modification. Although installing a CLI could be a supporting implementation detail, the supplied code provides no evidence connecting this installer to Kuaimai ERP. The downloaded script's contents are not supplied, so its subsequent actions cannot be determined.
The command streams a mutable remote script directly into Bash without verifying its integrity or authenticity beyond HTTPS. Compromise of the distribution endpoint could therefore execute attacker-controlled code with the invoking user's privileges, potentially exposing local files and credentials; this is a legitimate dependency setup path, not evidence of malicious intent.
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 directs the agent to execute downloaded shell or PowerShell code without an explicit installation approval step or an explanation of local system changes. Restricting setup to a missing-CLI error reduces exposure, but an ERP request does not itself authorize arbitrary local software installation; actual execution also depends on enforced tool permissions.
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