Security audit
Security checks for vulnerabilities and agentic risk
AccuLynx operations have clear approval controls, but setup can execute unreviewed software with broader agent changes that the skill does not explain.
Review and approve CLI installation separately, preferably using an inspected, pinned release. OOMOL will mediate access to your connected AccuLynx account. Preserve the required approvals for business-data changes, and review unwanted agent-skill synchronization; the publisher's [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md) documents OO_SKILLS_SYNC_DISABLED. Remote installer and connector behavior remain outside the verified artifact.
The supplied code installs software from Oomol, while the description promises AccuLynx operations. Nothing in the chunk establishes this installer as a supporting dependency for AccuLynx functionality. The remote script's contents are not provided, so its additional behavior cannot be assessed.
Piping a mutable remote installer directly into Bash executes its contents without a pinned version, integrity check, or review; the PowerShell alternative has the same weakness. Compromise of the installer endpoint or distribution infrastructure could yield arbitrary code execution with the invoking account's privileges, potentially exposing local files and credentials. HTTPS and conditional setup reduce some exposure but 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
The setup instructions direct immediate execution of downloaded shell and PowerShell code without explaining that this grants third-party code the agent's local execution privileges or requesting installation approval. The missing-command condition limits exposure, but the user-facing confirmation requirement covers AccuLynx writes rather than local software 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