Security audit
Security checks for vulnerabilities and agentic risk
The Kommo features fit the stated purpose, but setup can execute unverified downloads and introduce additional persistent agent skills without clearly explaining those changes.
Review and explicitly authorize the CLI installation before using the fallback setup, preferably using a verified, fixed release. Decide whether to permit automatic agent-skill synchronization; the CLI documents OO_SKILLS_SYNC_DISABLED as an opt-out. Connecting Kommo also entrusts OOMOL with access to your CRM data. The bundled instructions were fully inspected, but the remote installers and connector implementation were not verified.
The supplied chunk performs remote script execution rather than a Kommo data operation. Although installing dependencies can be a supporting implementation detail, no connection between this installer and the declared Kommo functionality is shown. The downloaded script's contents and effects cannot be determined from this chunk.
The curl-to-bash pipeline executes whatever script the installation URL returns, without pinning or independently verifying its contents. HTTPS protects transport but not against a compromised publisher or distribution endpoint, allowing arbitrary code execution with the user's permissions; this is the same underlying installation risk described in SQP-2.
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 setup directs execution of downloaded shell or PowerShell scripts without inspection, integrity verification, or explicit approval for installing software. If the distribution endpoint or delivery chain is compromised, attacker-controlled code could run with the invoking user's permissions; the missing-CLI condition limits exposure but does not eliminate it.
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