Security audit
Security checks for vulnerabilities and agentic risk
The Kling integration is clearly scoped, but its setup can run an unverified downloaded installer without asking first.
Review and install a trusted CLI release yourself before using this skill, and require approval for further installation steps. Check whether its automatic installation and synchronization of other agent skills is acceptable. Kling requests pass through OOMOL, and video generation may consume credits. The complete bundled artifact was inspected, but the external installers were unavailable for review.
The supplied code installs software from an Oomol-hosted endpoint rather than performing Kling AI operations. Nothing in the chunk establishes this installation as a supporting dependency for the declared purpose. The downloaded script's contents are not provided, so its further behavior cannot be determined.
Piping a mutable HTTPS installer directly into bash executes its contents without integrity verification or a review step. If the distribution endpoint or release pipeline is compromised, attacker-controlled code could access local files and credentials or establish persistence; the legitimate CLI dependency and conditional setup 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 fallback setup directs the agent to execute downloaded shell or PowerShell code without requiring explicit approval for software installation or explaining its local effects. Restricting this step to a missing-CLI error reduces exposure, but it still crosses from operating a connector into executing external code with the agent's local privileges.
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