Security audit
Security checks for vulnerabilities and agentic risk
Quentn changes require approval, but the CLI setup can introduce persistent changes to your agent environment that this skill does not explain.
Review the CLI installation and its automatic skill management before proceeding. Use a verified CLI release and, if you want to prevent startup changes to agent skills, set OO_SKILLS_SYNC_DISABLED=1 before invoking oo, as documented in the [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Quentn writes and deletions already require approval. The remote installer contents and resulting binary were not verified; no malicious behavior was established.
The supplied command installs external software rather than performing any visible Quentn operation. Installation could be a supporting implementation detail if its relationship to Quentn were established, but none is shown here. The downloaded script's contents and subsequent effects cannot be determined from this chunk.
Piping the HTTPS installer directly into bash executes mutable remote content without verifying its integrity or provenance. HTTPS protects transport but does not prevent a compromised publishing account or installer host from serving malicious code that could access local files and credentials; 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 directs the agent to execute remotely downloaded shell or PowerShell code without an integrity check or explicit approval for installing software. Although this is a legitimate prerequisite and only triggered when the CLI is missing, compromise of the installer delivery chain 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