Security audit
Security checks for vulnerabilities and agentic risk
The Zep workflow is coherent, but its automatic installation fallback executes unverified remote code and leaves broader agent changes undisclosed.
Review the installation fallback before enabling this skill. Install a verified CLI separately and consider disabling its automatic skill synchronization; the upstream command reference documents OO_SKILLS_SYNC_DISABLED. Expect sensitive Zep requests to pass through OOMOL, and retain confirmation for changes and deletions. The bundled artifact was fully inspected, but remote installer and binary behavior remain unverified. No malicious intent was established.
The supplied command performs remote script installation rather than any demonstrated Zep operation. Nothing in the provided code establishes this installer as a supporting dependency for Zep. The downloaded script's contents are unavailable, so its further effects cannot be determined.
The supplied chunk only invokes a login command; it contains no Zep operations or evidence that oo is a Zep client. Authentication could be a supporting implementation detail if that relationship were established, but the supplied content does not establish it.
The installation command executes a mutable remote script directly in Bash without verifying its contents, signature, or a trusted pinned digest; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint or delivery infrastructure could execute arbitrary code with the agent process's privileges, potentially accessing local files and credentials. The missing-CLI condition limits exposure, but no explicit user approval is required for this installation step.
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
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