Security audit
Security checks for vulnerabilities and agentic risk
The WeCom workflow includes clear approval controls, but its setup instructions can trigger unverified remote code execution without separate approval.
Install and verify a specific CLI release yourself before using this skill, and prevent automatic execution of its installer fallback. Review the CLI's agent-skill installation behavior and the permissions granted through OOMOL. Keep explicit approval for WeCom changes. The supplied artifact shows no malicious intent, but the external installer payload and its exact local changes remain unverified.
The supplied chunk executes an installer hosted on cli.oomol.com, not a WeCom MCP operation. Dependency installation can be a supporting implementation detail, but the supplied content establishes no relationship between this installer and the declared WeCom functionality. The downloaded script's contents are not supplied, so its further behavior and safety cannot be determined.
The command immediately executes mutable remote content without a pinned version or independently verified integrity; the PowerShell alternative has the same issue. A compromised installer endpoint or publishing pipeline could execute arbitrary code with the agent's local privileges, although the dependency-setup context and conditional trigger provide 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 missing-command fallback instructs the agent to install software without first obtaining approval for local system changes. Although conditional and connected to a legitimate dependency, this can expand a request to operate WeCom into executing installation code with the agent's local permissions; the declared tool allowlist may constrain execution but does not make the instruction safe.
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