Security audit
Security checks for vulnerabilities and agentic risk
The Livespace workflow includes useful safeguards, but its setup fallback runs unverified internet scripts without requiring your approval.
Review the setup fallback before installing. Install an independently reviewed, version-pinned CLI yourself and require approval for installer execution. OOMOL mediates the Livespace account connection; retain the skill's write and deletion confirmations. The downloaded installer contents and effects were not verified.
The supplied command installs software from an Oomol-hosted endpoint rather than performing Livespace operations. Nothing in the provided code establishes this installer as a supporting dependency for Livespace. The downloaded script's contents and subsequent effects are not supplied, so those effects cannot be assessed.
Piping an HTTPS response directly into Bash executes mutable remote content without integrity verification or review; the PowerShell alternative has the same weakness. Compromise of the installer distribution infrastructure could yield arbitrary execution with the agent's local privileges, exposing accessible files and credentials; HTTPS alone does not protect against a compromised origin.
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 recovery workflow directs the agent to execute remote installation scripts without requiring approval for code execution or system changes. Its conditional nature limits exposure, but routine setup can still become unauthorized local code execution; the Livespace write confirmations do not cover 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