Security audit
Security checks for vulnerabilities and agentic risk
The Lightfield integration is coherent, but its setup can execute unverified downloaded software without a clear approval step.
Review before installing. Install a verified, version-pinned oo CLI separately and require approval for software changes. Review its automatic skill synchronization, and connect Lightfield with only the permissions needed for your reads. The remote installers could not be inspected, so their exact local changes remain uncertain; the bundled artifact does not establish malicious intent.
The supplied code performs remote installer execution rather than Lightfield searching or reading. Nothing in the chunk establishes that installing the Oomol CLI is a supporting requirement for Lightfield access. The fetched script's contents are not supplied, so its further actions cannot be determined.
The command pipes a mutable remote script directly into Bash without verifying its contents, integrity, or version; the PowerShell alternative has the same weakness. If the distribution endpoint or delivery infrastructure is compromised, the installer can execute arbitrary code with the invoking user's privileges, potentially accessing local data and credentials. HTTPS and the legitimate dependency context do not establish artifact integrity.
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 the agent to install software without first explaining the local changes or obtaining explicit approval. The missing-command condition limits when this occurs, but a user requesting a Lightfield read has not necessarily authorized local software installation or execution of an external installer.
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