Security audit
Security checks for vulnerabilities and agentic risk
The BidSketch reader fits its stated purpose, but its setup fallback executes unverified remote installers without a clear approval step.
Review and install the CLI yourself before enabling this skill, including any bundled-skill installation or synchronization. Prefer a pinned, verified release and require approval for setup changes. Connecting BidSketch allows OOMOL-mediated access to business records. The complete bundled artifact was inspected; scanner reference gaps were harmless text examples, while external installer behavior remains unverified. No artifact-backed malicious behavior was found.
The supplied code does not search or read BidSketch data. Instead, it executes an installer from a different service. No connection to the declared BidSketch functionality is shown, so this is not established as a supporting implementation detail. The downloaded script's subsequent behavior cannot be determined from the supplied chunk.
Piping an HTTPS response directly into bash executes remote code with the agent process's local permissions, without a pinned version or independent integrity verification. A compromised distribution endpoint or malicious installer update could expose accessible files and credentials or modify the host; the Windows irm-to-iex example has the same underlying risk.
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 instructs the agent to install software by immediately executing downloaded code, without requiring user approval or explaining the resulting local system changes. Its missing-command prerequisite limits exposure, and the declared tool allowlist may block these commands, but neither makes the installation instructions safe if executed in a permissive environment.
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