Security audit
Security checks for vulnerabilities and agentic risk
Easy8 operations have clear approval safeguards, but setup can execute unverified remote software and introduce broader agent changes without separate consent.
Review and approve CLI installation separately, use a verified release, and review or disable automatic skill synchronization before running it. Connect only the intended Easy8 account and retain the documented write/delete approvals. The concern is insufficient control over setup; the artifact does not establish malicious intent. Remote installer behavior and the hosted backend remain unverified.
The supplied code performs remote installer execution rather than any visible Easy8 operation. Nothing in the supplied content establishes this installer as a supporting dependency for Easy8, and the declared description does not disclose software installation. The downloaded script's further behavior cannot be determined from this chunk.
Piping the installer directly from curl to bash executes mutable remote content without prior inspection or independent integrity verification. HTTPS protects transport but not against a compromised distribution endpoint, which could supply code that accesses local files and credentials with the executing user's permissions; the legitimate prerequisite context does not eliminate this supply-chain risk.
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 remotely downloaded shell or PowerShell scripts without explicit approval for local software installation. Although triggered only when the CLI is missing, this expands an Easy8 data task into local code execution and system changes; a compromised installer could execute with the agent'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