Security audit
Security checks for vulnerabilities and agentic risk
The account operations have clear approval safeguards, but setup can execute changing remote code and introduce persistent agent skills without clearly explaining those effects.
Review the setup behavior before enabling this skill. Install a reviewed, pinned CLI yourself and disable startup skill synchronization with OO_SKILLS_SYNC_DISABLED=1 if those agent-directory changes are unwanted. Connecting Nutrient DWS entrusts OOMOL with provider access; retain the required approvals and prefer restricted, short-lived tokens. The remote installers and connector implementation were unavailable for inspection. The supplied static scan reported no findings, but that does not resolve these concrete setup concerns.
The supplied chunk performs remote CLI installation rather than Nutrient DWS data operations. Dependency installation could be a supporting implementation detail, but nothing supplied establishes that this Oomol installer supports the declared purpose. The downloaded script is not included, so its additional effects cannot be determined.
The command pipes a mutable remote script directly into Bash without version pinning or independent integrity verification; the PowerShell alternative has the same execution pattern. If the distribution endpoint or publishing infrastructure is compromised, attacker-controlled code could execute with the agent process's permissions and access local files or credentials. The endpoint is relevant to the documented CLI dependency, but that legitimate purpose does not eliminate the 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
When the CLI is missing, the setup instructions direct the agent to execute a remote installer without first obtaining explicit approval for local software installation. Confirmation requirements for Nutrient DWS write operations do not cover this separate local side effect, although the missing-CLI condition limits when it occurs.
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