Security audit
Security checks for vulnerabilities and agentic risk
Zenkit operations have clear approval safeguards, but missing software triggers immediate execution of an unverified remote installer.
Review and approve CLI installation separately, preferably using a pinned, verified release. Check its bundled agent-skill installation and synchronization behavior, connect only the intended Zenkit account, and retain the existing write/delete approvals. The remote installers and hosted connector implementation were not inspected.
The supplied command executes an Oomol-hosted installer rather than performing any visible Zenkit operation. Although installing a dependency could be a supporting implementation detail, this chunk establishes no relationship between that installer and the declared Zenkit functionality. The downloaded script's contents and further effects cannot be determined from the supplied code.
Piping an HTTPS response directly into bash executes whatever the endpoint supplies without a review or integrity-verification step. HTTPS protects transport but does not protect against a compromised publisher or distribution endpoint, and this is the same underlying installation risk identified in SQP-2 rather than an independent exploit.
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 execution of remotely downloaded shell or PowerShell code without prior inspection, integrity verification, or explicit user approval for installing software. Restricting this to a missing-CLI error reduces exposure, but a compromised installer source could still execute arbitrary code with the invoking user's permissions; the issue is unsafe execution, not merely a missing warning.
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