Security audit
Security checks for vulnerabilities and agentic risk
The shipping workflow includes sensible safeguards, but its fallback setup directs the agent to execute unverified downloaded code without separate approval.
Review the CLI installation separately before enabling this skill. Prefer a verified, pinned release and check its automatic installation of other agent skills. Connect only the intended account and understand that shipping details are processed through OOMOL. The remote installer and CLI implementation remain outside the inspected artifact; no malicious behavior was established.
The supplied chunk performs remote software installation rather than a demonstrated Kuaidi100 operation. Nothing provided establishes this installer as a necessary supporting implementation detail for the declared purpose. The downloaded script is not included, so its further behavior cannot be assessed.
Piping the HTTPS response directly into Bash executes mutable remote code without release pinning or independent integrity verification; the PowerShell alternative has the same weakness. A compromised installer host or publishing pipeline could execute arbitrary commands with the user's permissions, although the documented dependency relationship provides no 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 setup workflow directs the agent to execute downloaded installation code when the CLI is missing, without requiring explicit approval for this local code execution and system modification. Restricting installation to a missing-dependency condition reduces exposure, but does not make a Kuaidi100 task sufficient authorization to run an installer with the invoking user's 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
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## Resources
- Kuaidi100 homepage: https://www.kuaidi100.com/
- API documentation: https://api.kuaidi100.com/document/how-to-use-mcp-service