Security audit
Security checks for vulnerabilities and agentic risk
Review before installing: setup can run downloaded software, and the required CLI can make broader changes to agent skills that this skill does not explain.
Review and approve the CLI installation separately, and control its automatic skill synchronization before use. Connect only the intended Luckin Coffee account and retain order confirmations. The bundled instructions show no malicious intent, but downloaded installer behavior and hosted connector internals remain unverified.
The supplied code executes a remote installation script, with no visible connection to Luckin Coffee or evidence that the installation supports the declared functionality. This is a materially different operation involving an inconsistent resource. The downloaded script's contents are not supplied, so its further effects cannot be determined.
The command executes the current contents of a remote script without version pinning or independent integrity verification; the PowerShell alternative has the same property. If the provider's distribution infrastructure is compromised, malicious code could run with the invoking user's permissions and access local files or credentials; HTTPS and the legitimate dependency relationship 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 missing-CLI fallback directs the agent to execute a remote installer without first obtaining approval for executing code and changing the local environment. Restricting setup to an actual missing-command error reduces exposure, but a user's request to operate a coffee account does not necessarily authorize software installation.
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