Security audit
Security checks for vulnerabilities and agentic risk
The Juniper Mist read actions fit the stated purpose, but setup executes unverified remote installers and the required CLI has undisclosed effects on other agent skills.
Review the CLI installation separately and use a verified release before connecting your account. Decide whether to allow additional agent skills; the CLI documents OO_SKILLS_SYNC_DISABLED=1 to prevent startup synchronization. Use a Juniper Mist account limited to the organizations, sites, and read permissions needed. OOMOL handles the connected credentials and requests. The external installer and hosted implementation were not verified, and no malicious behavior was established.
The supplied command performs remote script execution from an Oomol installation endpoint, not Juniper Mist search or read operations. Nothing in the supplied chunk establishes that this installer is a supporting dependency for the declared functionality. The downloaded script's further behavior cannot be determined from this chunk.
The command streams a mutable remote installer directly into Bash, giving the retrieved content immediate code execution without a pinned version or integrity check. HTTPS protects transport but does not protect against a compromised vendor endpoint or malicious release; this is the same underlying installation risk flagged by SQP-2.
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 pipe remotely retrieved scripts directly into Bash or PowerShell without inspection, integrity verification, or explicit approval for local software installation. If the distribution endpoint or delivery chain is compromised, this could execute attacker-controlled code with the agent process's privileges; restricting setup to a missing-CLI error reduces exposure but does not remove the risk.
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