Security audit
Security checks for vulnerabilities and agentic risk
The Detrack actions require sensible approvals, but setup can execute unverified software and introduce broader agent changes without clearly explaining them.
Review setup before installing. Use a reviewed CLI release and check or disable its automatic agent-skill synchronization before first use; the publisher documents that control in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Confirm that OOMOL may process your Detrack data, and retain approval for every write or deletion. The remote installers and hosted connector were not verified.
The supplied code performs remote script execution rather than any visible Detrack operation. Although installing a dependency can be a supporting implementation detail, this chunk establishes no relationship between the Oomol installer and the declared Detrack functionality. The downloaded script's contents and further effects are not available for assessment.
Piping a mutable remote installer directly into bash executes its contents without a verification step. HTTPS protects transport but does not protect against a compromised publisher or distribution endpoint; exploitation could compromise local files and credentials accessible to the invoking user. This is the same underlying installation risk identified by SQP-2, not an additional independent execution path.
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 execute downloaded shell or PowerShell code without verifying its integrity or obtaining explicit installation approval. Although legitimate dependency setup and the missing-command prerequisite reduce exposure, a compromised distribution endpoint could execute arbitrary code 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