Security audit
Security checks for vulnerabilities and agentic risk
The HubSpot features have sensible safeguards, but setup can execute unverified remote software without separate approval.
Review and explicitly approve a verified CLI release before allowing setup, including any installation of additional agent skills. Connecting HubSpot authorizes OOMOL-mediated account access; grant only needed permissions and retain confirmation for CRM changes. The remote installer and live connector code were not available in the reviewed artifact.
The supplied code performs remote software installation rather than HubSpot data operations. Although dependency installation can be a supporting implementation detail, nothing in this chunk establishes that this installer supports the declared HubSpot functionality. The downloaded script's further behavior is not visible and cannot be assessed.
The command pipes a mutable remote installer directly into Bash without verifying a pinned version, signature, or independently trusted digest; the PowerShell alternative has the same underlying issue. Compromise of the installation endpoint or delivery pipeline could execute arbitrary code with the invoking user's privileges, potentially exposing local credentials and files. The legitimate dependency and conditional fallback reduce suspicion of malicious intent but do not eliminate this supply-chain 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 directs installation of local software without requiring informed user approval or explaining potential system changes. A request to operate HubSpot does not necessarily authorize installing software; limiting installation to a missing-CLI error reduces frequency but does not establish consent.
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