Security audit
Security checks for vulnerabilities and agentic risk
The data-search workflow is coherent, but its setup can execute changing remote code and introduce broader changes to your agents’ installed skills.
Review the setup before enabling this skill. Prefer a verified, preinstalled CLI and explicitly control its automatic skill synchronization. Only submit identifiers and queries you intend to share through OOMOL with People Data Labs, and check usage charges. The remote installers could not be inspected, and current publisher documentation cannot establish the behavior of every downloaded version.
The supplied command performs remote script execution and apparently installs an Oomol CLI; it does not search or read People Data Labs data. No evidence establishes this installer as a supporting dependency for the declared purpose. The downloaded script's additional behavior cannot be determined from the supplied code.
The setup instructions pipe a remotely fetched, unpinned script directly into Bash without integrity verification or an explicit approval step; the PowerShell alternative has the same execution pattern. If the distribution endpoint or its supply chain is compromised, a missing-CLI error can lead to arbitrary code execution with the agent process's permissions, despite the skill's otherwise read-oriented purpose.
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 submit action payloads and labels all untagged reads as safe to run directly. Person-enrichment and search requests can include personal identifiers or sensitive search criteria transmitted through OOMOL to People Data Labs, but the skill does not warn users about that disclosure; read-only operations can still affect privacy.
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