Security audit
Security checks for vulnerabilities and agentic risk
The LeadMagic functions fit the stated purpose, but setup executes unverified downloads and leaves broader changes to agent skills insufficiently disclosed.
Review setup before enabling this skill. Install a reviewed CLI version yourself and control whether it installs or synchronizes other agent skills. Send only identifiers you intend to share with OOMOL and LeadMagic. The remote installers and hosted connector implementation were not verified; the Review verdict concerns setup authority and disclosure, not demonstrated malicious intent.
The supplied code contains no LeadMagic operations or demonstrated connection between the Oomol installer and the declared purpose. Downloading and executing an unrelated installer is a materially different capability, not an established supporting implementation detail. The downloaded script's contents and subsequent effects are not available for inspection.
The curl-to-bash command executes mutable remote content immediately, without artifact integrity verification or review. Although the URL belongs to the documented CLI provider and installation is only a fallback, compromise of that distribution path could expose local files and credentials or modify the system; this is the same underlying issue as the fallback-installation finding.
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 workflow instructs the agent to execute connector actions with JSON inputs, which can include email addresses, profile URLs, and personal identifiers. Although the connector providers are named, there is no privacy warning about transmitting these inputs through OOMOL to LeadMagic, and the safety section characterizes all untagged reads as safe to run directly.
The fallback instructs the agent to execute downloaded shell or PowerShell scripts without inspecting them or verifying a pinned artifact. A compromised installer endpoint or release could therefore execute arbitrary code with the agent's privileges; the missing-CLI condition limits exposure but does not remove the risk.
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