Security audit
Security checks for vulnerabilities and agentic risk
The Gong read functions fit their purpose, but fallback setup directs the agent to execute an unverified remote installer without separate user approval.
Review the fallback installer before use. Install a verified CLI release yourself or require explicit approval before the agent installs it, and ensure your organization permits OOMOL to access Gong data. No artifact evidence establishes malicious intent, but the remote installer's behavior remains unverified.
The supplied code performs remote installer execution rather than Gong data access. Nothing in the chunk establishes this installer as a supporting dependency for the declared Gong functionality. The downloaded script is not provided, so its subsequent behavior cannot be determined.
Piping a live HTTPS response into Bash executes mutable remote code with the agent process's local privileges, without artifact pinning or independent integrity verification. Compromise of the distribution endpoint or release pipeline could expose locally accessible data or modify the system; the PowerShell alternative has the same underlying risk, despite the legitimate dependency-installation context.
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 the agent to execute a remote installer without first obtaining approval for local code execution and system changes, which exceeds the normal expectations of a Gong read request. Requiring a missing-CLI error limits when this occurs, but does not authorize installation or explain its risks; actual execution also depends on the host's tool 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