Security audit
Security checks for vulnerabilities and agentic risk
The DealMachine features fit their stated purpose, but setup can automatically run unverified installer code with broader effects on your agent environment.
Review and install a verified CLI release yourself before use, rather than allowing automatic installer execution. Consider disabling managed skill synchronization if you only want this DealMachine integration. OOMOL mediates your connected-account access, and searches or enrichment may consume credits. The complete bundled artifact was inspected, but the remote installers and hosted connector implementation were not verified.
The supplied command executes an Oomol-hosted installer rather than searching or reading DealMachine data. Nothing in the supplied code establishes this installation as a supporting dependency for the declared functionality. The remote script's contents and any further effects are not visible.
Piping a remotely fetched script directly into Bash executes whatever the endpoint returns with the invoking user's privileges, without a pinned version or independent integrity check. A compromised distribution endpoint could therefore execute arbitrary code and access local data; the PowerShell alternative has the same weakness. The legitimate dependency-installation context and missing-CLI condition limit exposure but do not establish script integrity.
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 an installer without first obtaining approval for local system changes or explaining that remote code will run. Restricting this to a command-not-found error reduces exposure, but a DealMachine data request does not itself authorize software installation.
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