Security audit
Security checks for vulnerabilities and agentic risk
The Foursquare features are coherent, but setup executes unverified downloaded code without clearly scoped user approval.
Review and install the CLI separately before enabling this skill, checking its bundled-skill synchronization settings and local changes. The external installer and exact downloaded release were not verified. Use only location and search information you intend to share through OOMOL with Foursquare. No artifact evidence establishes malicious intent.
The supplied chunk performs remote installer execution, not Foursquare data access. Nothing in the chunk establishes that this installation is a supporting dependency for the declared functionality. The downloaded script's contents are unavailable, so its further behavior cannot be determined.
The command pipes a mutable remote response directly into Bash, allowing that response to run arbitrary code with the invoking user's permissions. HTTPS protects transport but does not protect against compromise of the publisher or distribution infrastructure; this is the same underlying installation risk identified in the setup finding, not an additional independent vulnerability.
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 input payloads, including latitude and longitude for nearby-place lookups. Although OOMOL and Foursquare are identified, the skill does not warn that these inputs can disclose sensitive user location or search information to those services; labeling reads as safe overlooks that privacy impact.
Both setup examples execute remotely downloaded scripts immediately, without an inspection step, pinned version, or independently verified integrity. A compromised distribution endpoint or malicious installer update could execute arbitrary commands with the invoking user's privileges; limiting setup to a missing-CLI error reduces exposure but does not eliminate it.
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