Security audit
Security checks for vulnerabilities and agentic risk
The TextIt workflow has clear safeguards, but setup directs the agent to execute downloaded software without separate approval or integrity checks.
Review setup before installing. Install a reviewed, pinned CLI yourself and require approval before any downloaded installer runs. Consider disabling the CLI's automatic skill synchronization using OO_SKILLS_SYNC_DISABLED=1, as documented in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). OOMOL will process the TextIt data used by requested actions. Check message recipients and deletion targets carefully. The remote installer payloads remain unverified.
The supplied chunk executes an Oomol-hosted installer and contains no TextIt interaction or evidence that this installation supports TextIt operations. Its observable behavior therefore differs materially from the declared purpose. The downloaded script's contents and subsequent effects are not available for assessment.
Piping an HTTPS download directly into bash executes whatever the installation endpoint returns without an independent integrity check or opportunity for review. A compromised distribution endpoint or altered installer could execute arbitrary commands with the invoking user's privileges, including accessing local data; the domain is relevant to the connector, but that does not establish the integrity of its current response.
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 setup instructions direct execution of downloaded shell or PowerShell code without requiring integrity verification or explicit approval for local system changes. The confirmation rules cover TextIt mutations, not installation, potentially allowing a routine TextIt request to trigger arbitrary installer code with the agent's local privileges; 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