Security audit
Security checks for vulnerabilities and agentic risk
The Jungle Scout workflow is coherent, but automatic setup executes unverified remote code and leaves broader changes to agent skills insufficiently explained.
Review setup before enabling this skill. Install a verified CLI release yourself and require approval for future installation changes. OOMOL mediates requests and stores the connected provider credentials. To prevent documented startup skill synchronization, upstream provides OO_SKILLS_SYNC_DISABLED=1; see its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). The remote installers were unavailable for inspection; no malicious behavior was established in the bundled artifact.
The supplied command installs or bootstraps software from Oomol rather than searching or reading Jungle Scout data. Nothing in the chunk establishes this installation as a supporting dependency for the declared purpose. The remote script's contents are not supplied, so its further behavior cannot be determined.
Piping an HTTPS response directly into bash executes whatever the installation endpoint returns, without a pinned version or independent integrity verification. Compromise of the distribution endpoint could therefore lead to arbitrary code execution and access to local data or credentials; the endpoint's documented role as the CLI distributor explains its use but does not eliminate this 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 instructs the agent to execute downloaded shell or PowerShell code without a verification step or explicit approval for installing software. Restricting this to a missing-CLI error reduces exposure, but a compromised installer source could still execute arbitrary code with the invoking user's permissions; the missing warning alone is not the core vulnerability.
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