Security audit
Security checks for vulnerabilities and agentic risk
The PassSlot operations have clear approval safeguards, but setup can execute unverified downloaded code and introduce persistent agent changes without clear user control.
Review setup before use and install a verified CLI release yourself. OOMOL mediates your PassSlot access, so connect only the account permissions needed. The publisher documents OO_SKILLS_SYNC_DISABLED=1 to prevent automatic skill-file synchronization in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Keep the skill's approval requirements for writes and deletion. The downloaded installers were unavailable for inspection, so their exact effects remain unverified.
The supplied code performs remote installer execution rather than any visible PassSlot operation. Although installation can be a supporting implementation detail, nothing supplied establishes that this installer supports PassSlot. The remote script's contents and any additional effects cannot be determined from this chunk.
Piping a mutable remote installer directly into bash executes its contents with the invoking user's privileges, without version pinning or artifact verification. HTTPS protects transport but does not prevent a compromised hosting service or publisher from supplying code that steals accessible credentials or modifies local files; the PowerShell example has the same underlying 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
When the CLI is missing, the skill directs execution of remotely downloaded shell or PowerShell code without first obtaining informed approval for local software installation. The setup is conditional and relevant to the task, but it crosses from PassSlot operations into potentially broad local system changes without an explicit consent boundary.
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