Security audit
Security checks for vulnerabilities and agentic risk
The Streak functions fit the stated purpose, but fallback setup can execute a remote installer without a separate approval step.
Review and approve CLI installation separately before allowing setup to run. Prefer a verified release and check whether the CLI installs or updates other agent skills. Connecting Streak gives OOMOL access to the authorized business data. The sole bundled file was fully inspected; the remaining uncertainty concerns external installer and CLI behavior. No artifact-backed malicious behavior was found.
The supplied chunk performs no Streak search or read operation. Instead, it executes an external installer, with no demonstrated connection to the declared Streak functionality. Although dependency installation can be a supporting implementation detail, the supplied content does not establish that relationship. The downloaded script's further behavior cannot be determined from this chunk.
Piping a remotely fetched, unpinned script directly into bash executes whatever the endpoint supplies with the invoking user's privileges. HTTPS protects transport but does not protect against a compromised publisher or modified installer, which could expose local credentials or files; the PowerShell setup uses the same download-and-execute pattern.
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 instructs the agent to install software after a command-not-found error without requiring approval for executing an installer or changing the local environment. A request to read Streak data does not itself authorize arbitrary installer execution; the conditional trigger and Bash(oo *) tool restriction reduce reachability but do not make the setup instructions safe.
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