Security audit
Security checks for vulnerabilities and agentic risk
The LeadBoxer lookups fit the stated purpose, but setup directs execution of remote installation code without clear user approval.
Review and approve the CLI installation separately before allowing the setup fallback, preferably using a verified, fixed release. Check its automatic agent-skill installation and synchronization settings. OOMOL mediates your lookup requests and connected credentials. The remote installers and hosted connector implementation were not verified; the supplied artifact does not establish malicious intent.
The supplied chunk performs remote installer execution, not LeadBoxer searching or reading. Nothing in the supplied code establishes that this installer is a supporting dependency for the declared functionality. The downloaded script's contents are not supplied, so its further behavior cannot be assessed.
Piping a live HTTPS response directly into Bash executes whatever code the endpoint serves without version pinning, integrity verification, or an opportunity to review it. Compromise of the distribution endpoint could therefore yield arbitrary code execution with the agent's local privileges; the PowerShell alternative has the same risk, although neither command alone proves malicious intent.
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 missing-CLI fallback directs the agent to execute a remote installer without first explaining its local effects or obtaining installation approval. A LeadBoxer read request does not inherently authorize installing executable software, and the installer could modify files or shell configuration with the invoking user's privileges; the conditional trigger reduces exposure but does not remove this 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