Security audit
Security checks for vulnerabilities and agentic risk
The Helium 10 workflow fits its purpose, but setup can execute unverified downloaded code and introduce broader changes to installed agent skills.
Review setup before enabling this skill. Install a reviewed CLI release separately and require approval for software installation. Consider disabling automatic skill synchronization with OO_SKILLS_SYNC_DISABLED=1, as documented in the [CLI reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). OOMOL mediates the connected-account workflow; its installer and connector implementation are not bundled here. The artifact supports setup and disclosure concerns, but does not establish malicious intent.
The supplied chunk consists solely of remote installer execution. It contains no visible Helium 10 integration or data access, and nothing supplied establishes that this installer is a supporting dependency for the declared purpose. The downloaded script's contents and subsequent effects cannot be determined from this chunk.
Piping an HTTPS response directly into bash executes mutable remote content without prior inspection or authenticated version verification. Compromise of the installation endpoint or its delivery infrastructure could execute attacker-controlled code with access to local files and credentials; this is a supply-chain risk, not evidence that the current script is malicious.
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 execute downloaded shell or PowerShell code without explicit approval for installing software or changing the host. Although limited to a missing-CLI condition, it can turn an ordinary data-reading request into arbitrary code execution with the agent process's permissions.
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