Security audit
Security checks for vulnerabilities and agentic risk
Userlist changes require approval, but setup can execute unverified remote code and introduce undisclosed changes to other agent skills.
Review the setup behavior before enabling this skill. Prefer installing a reviewed CLI release yourself and confirm that OOMOL may process your Userlist data and credentials. To prevent startup changes to other agent skills, the publisher documents OO_SKILLS_SYNC_DISABLED=1; configure it before invoking the CLI. [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Keep the existing approval requirement for data changes and messages. The remote installers could not be inspected; no malicious behavior was established.
The supplied command installs software from Oomol rather than performing Userlist operations. Nothing in the supplied chunk establishes that this installer is a supporting dependency for Userlist, so its behavior is not adequately represented by the declared purpose. The downloaded script's further behavior cannot be determined from this chunk.
The supplied chunk's sole action is an authentication command, with no indication that oo is associated with Userlist. Authentication could be a supporting implementation detail if that connection were established, but the supplied content does not establish it and does not substantiate the declared Userlist purpose.
Piping an unpinned HTTPS response directly into bash executes whatever code the installer endpoint supplies with the invoking process's permissions. Compromise of that endpoint or its delivery pipeline could expose local files and credentials or enable persistent modifications; HTTPS alone does not establish release integrity, although execution is only prescribed when the CLI is missing.
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 missing-CLI fallback directs installation through immediate execution of remotely fetched shell or PowerShell code without requiring informed approval for local system changes. Its conditional nature limits exposure, but the write-confirmation rules concern Userlist state and do not explicitly protect local installation.
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