Security audit
Security checks for vulnerabilities and agentic risk
The data-reading workflow fits its purpose, but setup tells the agent to execute downloaded code without verification or a clear user approval step.
Review the setup behavior before installing. Install a reviewed, version-specific oo release yourself or require approval and verification before the agent runs an installer. Gangtise requests use your OOMOL-connected account, so review its permissions and billing. The bundled instructions show no malicious behavior, but the remote installer's effects remain unverified.
The supplied chunk executes an external installer rather than implementing the declared search-and-read behavior. Dependency installation can be a supporting implementation detail, but nothing supplied establishes this installer's role in accessing Gangtise. The downloaded script is not provided, so its further behavior and any maliciousness cannot be determined.
Piping a live HTTPS response directly into bash executes mutable remote code without a pinned version, independently verified integrity, or an inspection step; the PowerShell alternative has the same problem. The domain is relevant to the documented dependency, but compromise of its hosting or release pipeline could still result in arbitrary code execution with access to local files and credentials.
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 missing-CLI fallback instructs the agent to execute downloaded shell or PowerShell code without first obtaining approval for local code execution and installation changes. Although this is a legitimate dependency-setup context, a request to read financial data does not necessarily authorize installing software, and a compromised installer could execute with the invoking user's 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