Security audit
Security checks for vulnerabilities and agentic risk
The Gainsight operations have clear approval controls, but setup can execute changing remote code and introduce broader agent changes without separate approval.
Review setup before installing: verify a specific CLI release and review or disable its automatic installation of other agent skills. Connect a suitably restricted Gainsight account and retain the required approval for every write or deletion. The bundled instructions were fully inspected; remote installer and hosted connector implementations remain unverified.
The supplied chunk installs software from cli.oomol.com rather than performing Gainsight NXT data operations. Dependency installation can be a supporting implementation detail, but this chunk provides no evidence linking the installer to the declared Gainsight functionality. The downloaded script's contents and additional effects cannot be determined from the supplied code.
The command immediately executes a mutable script downloaded from an external server without version pinning or independent integrity verification. Compromise of the distribution endpoint could execute arbitrary code with the invoking user's permissions; HTTPS protects transport but does not establish that the script is trustworthy. The PowerShell installation example has the same weakness.
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 install software when the CLI is missing without explicitly obtaining permission for local system changes. Although installation supports the legitimate connector workflow and only occurs conditionally, a request to operate on Gainsight records does not necessarily authorize installing and executing software on the host.
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