Security audit
Security checks for vulnerabilities and agentic risk
Memberstack changes require approval, but setup runs unverified downloads and omits broader changes the CLI can make to your agents.
Review the CLI installation separately before allowing automatic setup. Memberstack data passes through OOMOL; confirm exact changes, especially deletion and Stripe cleanup. To prevent startup skill synchronization, the publisher documents OO_SKILLS_SYNC_DISABLED=1 in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Remote installer contents and hosted connector behavior remain unverified.
The supplied code executes an Oomol-hosted installer and contains no Memberstack API calls or data operations. No connection is established between this installation and the declared Memberstack functionality, so this is an undeclared capability involving an inconsistent resource. The remote script's contents and further effects cannot be determined from the supplied chunk.
Piping the HTTPS response directly into bash executes mutable remote content without an inspection or integrity-verification step. Although the domain belongs to the CLI provider and installation supports the Memberstack workflow, compromise of the distribution endpoint could expose local files and credentials or allow persistent system changes under the user's privileges.
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 code without integrity verification or explicit approval for local software installation. A compromised installer source could execute arbitrary code with the invoking user's privileges; the missing-CLI condition limits exposure but does not make execution safe.
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