Security audit
Security checks for vulnerabilities and agentic risk
The travel searches fit the stated purpose, but automatic setup executes unverified remote code and leaves broader agent changes undisclosed.
Review and install the CLI separately before using this skill. Verify the downloaded release and decide whether automatic skill synchronization across your agents is acceptable; upstream documents OO_SKILLS_SYNC_DISABLED=1 to disable startup synchronization. Searches use your OOMOL-connected account and may consume credit. The remote installer was unavailable for inspection, so its exact changes remain uncertain. No malicious intent or exfiltration was established.
The supplied chunk performs remote script execution and contains no Tongcheng search or read operation. Although installation can support a skill, the provided content does not establish that this installer is a supporting dependency for the declared purpose. The downloaded script's contents and subsequent effects are not available for assessment.
Piping the HTTPS response directly into bash executes mutable remote content without an independently verified signature or pinned artifact. Although the URL is consistent with the documented CLI provider, compromise of its hosting or release pipeline could execute attacker-controlled code with the agent's permissions, exposing accessible files and credentials; the PowerShell alternative has the same 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 directs the agent to execute downloaded shell or PowerShell code without first explaining the system changes or obtaining installation approval. Restricting this behavior to a missing CLI reduces its frequency, but dependency installation still expands a read-only search task into potentially arbitrary code execution under the agent's account.
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