Security audit
Security checks for vulnerabilities and agentic risk
The Linkly actions have clear safeguards, but setup directs remote code execution without clear approval and may introduce broader changes to your agent.
Review the setup behavior before installing. Install a verified CLI version separately, review or disable its automatic skill synchronization, and understand that OOMOL processes the Linkly requests. Keep the skill's confirmation requirements for changes and deletion. The concern is uncontrolled setup and broader agent changes; the artifact does not establish malicious intent.
The supplied command targets Oomol infrastructure rather than Linkly and executes an external installer. Nothing in the supplied chunk establishes this installation as a supporting dependency for Linkly functionality. The remote script's contents are unavailable, so its specific effects cannot be determined.
The command pipes a mutable remote script directly into Bash without verifying its contents, signature, or version; the PowerShell alternative has the same weakness. If the distribution endpoint or delivery pipeline is compromised, the installer can execute attacker-controlled code with the agent's local privileges, exposing accessible files and credentials. The legitimate dependency context and missing-command prerequisite reduce exposure but do not establish script integrity.
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 install software after a missing-command error without requiring approval for local system changes. Although this is a legitimate dependency and only a conditional fallback, a request to manage Linkly data does not necessarily authorize installing software or executing a downloaded installer.
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