Security audit
Security checks for vulnerabilities and agentic risk
The Octave integration fits its purpose, but setup can execute remote code and introduce broader agent changes without clear approval.
Review the CLI installation and its changes to other agent skills before allowing setup. Prefer a reviewed, pinned installation, connect only the intended Octave workspace, and retain confirmation for data changes. Requests pass through OOMOL. The remote installer contents and hosted connector implementation were not verified; the concerns support review, not a conclusion of malicious intent.
The supplied command performs remote software installation, not Octave data operations. Nothing in the provided content establishes Oomol as a supporting dependency for Octave. The downloaded script is not supplied, so its further behavior cannot be assessed.
Piping a remote installer directly into Bash executes mutable network-delivered code with the invoking user's privileges, without a pinned version or independent integrity verification. A compromised distribution endpoint could therefore execute arbitrary commands and access local data or credentials; HTTPS and the legitimate dependency relationship do not eliminate that supply-chain 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
The fallback directs the agent to install software through remotely supplied shell or PowerShell code without requiring approval for local system changes. Restricting installation to a missing-CLI error reduces exposure, but a request to operate Octave does not necessarily authorize installing software on the host.
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