Security audit
Security checks for vulnerabilities and agentic risk
The Maps features fit their purpose, but setup can execute unverified remote code and introduce additional agent skills without clearly explaining those changes.
Review and install a specific CLI version separately before use. If you only want Maps support, disable automatic skill synchronization before invoking the CLI. Location queries pass through OOMOL to Google, and usage may incur charges. This review covered the complete packaged skill; the remote installers and deployed connector implementation remain unverified.
The supplied command performs remote script execution, not Google Maps searching or data retrieval. Nothing in the chunk establishes that installing the Oomol CLI is a supporting requirement for the declared purpose. The downloaded script's contents and subsequent effects are not provided.
The setup instructions pipe a remotely fetched, unpinned script directly into Bash without integrity verification or review; the PowerShell alternative has the same execution pattern. A compromised distribution endpoint or malicious installer update could execute arbitrary commands with the agent's local privileges, exposing files and credentials, although the missing-CLI prerequisite limits when this path is reached.
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 workflow instructs the agent to submit action payloads, which can include user-provided addresses, coordinates, and route endpoints. Although the connector architecture is described, the skill does not warn that these potentially sensitive inputs are transmitted to OOMOL and Google; its blanket statement that read actions are safe to run directly overlooks this privacy impact.
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