Security audit
Security checks for vulnerabilities and agentic risk
The Leadfeeder functions fit the stated purpose, but setup directs the agent to execute changing remote code without a clear user checkpoint.
Review and install the CLI yourself before use, control any automatic skill synchronization, and connect only the intended Leadfeeder account. Consider whether you trust OOMOL to process your requests and connected-account access. The complete bundled artifact was inspected, but the changing installer and backend behavior remain unverified. No artifact-backed malicious behavior was found.
The supplied code performs remote script execution for an Oomol CLI installation, while the description promises Leadfeeder data access. No connection between this installation and the declared functionality is established in the supplied chunk. The remote script's contents and any additional effects cannot be determined from this code alone.
Piping a remotely fetched script directly into Bash executes mutable external code without a pinned version, independent integrity verification, or inspection; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint or release process could execute attacker-controlled commands with the agent's local permissions, although this path is conditional on the CLI being absent.
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 without first obtaining approval or explaining that installation executes code and changes the local environment. Restricting setup to a missing-command error reduces exposure, but a request to read Leadfeeder data does not itself authorize software 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