Security audit
Security checks for vulnerabilities and agentic risk
The location lookups fit the skill’s purpose, but automatic setup executes unverified downloaded software and can introduce additional agent skills without clearly disclosing those changes.
Review and install a fixed CLI release yourself before enabling this skill. Check whether you want its additional agent skills; the publisher documents OO_SKILLS_SYNC_DISABLED=1 to disable startup synchronization in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Share only location information you intend OOMOL and Positionstack to receive. The bundled instructions were fully inspected, but remote installers and hosted implementation remain unverified.
The supplied command performs remote code execution for an apparent CLI installation, not a Positionstack operation. Nothing in the supplied chunk establishes that this installation is a supporting requirement for Positionstack access. The downloaded script is not supplied, so its additional behavior cannot be assessed.
The supplied code performs a CLI login rather than a Positionstack search or data-read operation. Authentication could be a supporting implementation detail if tied to Positionstack, but the supplied chunk establishes no such connection.
The setup instructions pipe a mutable remote script directly into Bash without version pinning or independent integrity verification; the PowerShell alternative has the same weakness. If the distribution endpoint or its publishing pipeline is compromised, following these instructions could execute attacker-controlled code with the agent's local permissions, exposing files and credentials. The missing-CLI condition limits exposure but does not make execution safe.
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 execute connector actions with payloads that can contain addresses, coordinates, or IP addresses. Although it identifies OOMOL and Positionstack, it does not warn that these potentially sensitive inputs are transmitted to external services; the safety section instead treats read actions as safe to run directly.
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