Security audit
Security checks for vulnerabilities and agentic risk
The Gorgias read functions fit the stated purpose, but missing software triggers instructions to run downloaded installers without a separate approval step.
Review the setup behavior before installing. Require explicit approval before downloaded installers run, preferably installing a reviewed, version-pinned CLI yourself. Connecting Gorgias authorizes OOMOL to mediate access to private helpdesk data. The remote installers were unavailable for inspection, so their exact local changes remain unverified.
The supplied command performs remote script execution rather than searching or reading Gorgias data. No Gorgias integration or dependency relationship is shown that would establish this installation as a supporting implementation detail. The downloaded script's contents and any further effects cannot be determined from this chunk.
The command pipes a mutable remote script directly into Bash without integrity verification or review; the PowerShell alternative has the same weakness. If the distribution endpoint or release pipeline is compromised, attacker-controlled code would execute with the invoking user's privileges, potentially accessing local credentials and files; HTTPS does not protect against a compromised publisher.
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 an agent to install software after a missing-command error without explicitly requesting approval for executing remote code or modifying the local environment. Although conditional setup makes this less concerning than unconditional execution, a request to read Gorgias data does not inherently authorize local 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