Security audit
Security checks for vulnerabilities and agentic risk
The messaging workflow requires confirmation, but setup can execute unverified software without clear approval and introduce additional agent skills.
Review and approve CLI installation separately, using a verified release and checking which additional skills it installs. Keep confirmation enabled for message recipients and content, and consider what information passes through OOMOL. The sole bundled artifact was fully inspected, but the remote installers could not be retrieved; their exact behavior remains uncertain. No artifact-backed malicious behavior was established.
The supplied chunk performs no visible Feishu Custom Bot operations. Its sole action is to fetch and execute an external installer, and nothing supplied establishes that installation as a supporting requirement for the declared functionality. The downloaded script's contents and effects cannot be determined from this chunk.
Piping a mutable remote script directly into bash executes its contents with the agent process's local permissions without a separate verification step. HTTPS protects transport but does not prevent a compromised distribution endpoint from serving malicious code capable of accessing local files or credentials; the conditional setup limits exposure but does not remove this 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 fallback directs the agent to execute remote installation scripts without requiring informed approval for local code execution and system changes. Although installation is a legitimate prerequisite and only occurs after a missing-command error, the Feishu write-confirmation rules do not explicitly cover this local 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