Security audit
Security checks for vulnerabilities and agentic risk
The data-search workflow fits its purpose, but fallback setup directs the agent to execute unverified remote installers without clear user control over local changes.
Review setup before enabling this skill. Prefer a separately approved, version-pinned CLI installation with verified integrity, and check which agent skills it installs or updates. DataForB2B requests use your OOMOL-connected account and may consume service credits. The Review verdict concerns installation control and broader local changes, not evidence of malicious intent.
The declared purpose concerns DataForB2B data access, while the code executes an installer hosted on cli.oomol.com. Nothing supplied establishes this installer as a supporting dependency for DataForB2B. The remote script's contents and downstream effects are unknown, but downloading and executing it is directly observable and is not represented by the description.
Piping an HTTPS response directly into Bash executes mutable remote content without an independently verified digest, signature, or pinned version. Compromise of the installer hosting or release process could execute arbitrary code with the agent's permissions, potentially exposing accessible files and credentials; the PowerShell fallback has the same trust problem.
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 remote installation scripts without explicitly obtaining approval for local code execution and system changes. Conditional execution limits exposure, but a request to read business data does not necessarily authorize installing software with the agent's local permissions.
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