Security audit
Security checks for vulnerabilities and agentic risk
PractiTest changes require approval, but automatic installation and undisclosed changes to local agent skills need review.
Review and install a verified CLI release separately before use. Account for its automatic changes to agent skills; the publisher documents OO_SKILLS_SYNC_DISABLED=1 to suppress startup synchronization. Use a narrowly scoped PractiTest connection and retain approval for every write or deletion. The remote installers and deployed connector were not verified. [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables)
The supplied command runs an external installer rather than performing PractiTest operations. Nothing in the provided chunk establishes that this installer is a supporting dependency for PractiTest. The remote script's contents are unavailable, so its further behavior cannot be determined.
Piping the HTTPS installer directly into bash executes whatever the remote endpoint returns without a pinned artifact or independent authenticity check. HTTPS protects transport but does not prevent a compromised publisher or distribution endpoint from delivering malicious code; this is the same underlying installation risk as SQP-2.
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 execute remotely retrieved shell or PowerShell code without prior inspection, integrity verification, or explicit installation approval. Although execution is conditional on a missing CLI, a compromised distribution endpoint could supply code that runs with the agent's local permissions and accesses files or credentials.
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