Security audit
Security checks for vulnerabilities and agentic risk
The Lattice read workflow fits its purpose, but its setup fallback runs downloaded installation code without verification or a separate approval step.
Review and approve the CLI installation separately before allowing the agent to run it, including any changes to installed agent skills. Prefer a fixed release with verified integrity. Use only necessary Lattice permissions and consider OOMOL's access to workplace data. The sole bundled artifact was fully inspected, but the external installer and CLI implementation were not verified.
The supplied code performs remote installer execution rather than Lattice search or read operations. Nothing in the chunk establishes this installer as a necessary supporting component for Lattice access. The downloaded script's contents are not supplied, so its subsequent actions cannot be determined.
The curl-to-bash command executes a mutable remote script without verifying its integrity or authenticity independently of HTTPS; the PowerShell alternative has the same weakness. If the distribution endpoint or release process is compromised, executing this fallback could run attacker-controlled code with the invoking user's privileges, exposing local data and credentials.
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 instructs installation through immediate execution of downloaded code without first explaining the system changes or obtaining user approval. Although limited to a missing dependency, this expands a Lattice read request into local software installation; the declared oo-only tool allowance may constrain execution but does not make the installation instructions 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