Security audit
Security checks for vulnerabilities and agentic risk
The football-data actions fit the stated purpose, but setup directs the agent to execute downloaded installers without integrity checks or clear user approval.
Review and approve CLI installation separately before allowing setup to proceed. Prefer a verified, fixed release and check whether it installs or updates other agent skills. OOMOL sign-in and possible charges are disclosed dependencies. The remote installers and hosted connector implementation were not verified; no malicious behavior is established by the bundled artifact.
The supplied command performs remote installer execution, not OpenFootball World Cup data retrieval. Nothing in the supplied chunk establishes this installation as a supporting dependency for the declared functionality. The downloaded script's further actions are not visible and cannot be assessed.
The supplied code only invokes authentication; it contains no World Cup search or read operation and establishes no connection to the declared data source. Authentication can be a supporting implementation detail, but here it is the entirety of the supplied behavior rather than support for an implemented data-access operation.
Piping a live download directly into Bash executes whatever the installation endpoint returns with the invoking user's privileges, without version pinning or independent integrity verification. HTTPS protects transport but not a compromised publisher or distribution endpoint; exploitation could expose accessible credentials and modify local files, far beyond the skill's read-only purpose.
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 instructs an agent performing a read-only data task to execute a remote installer without a separate warning or explicit approval for local code execution and system changes. Its missing-command trigger limits exposure, but does not establish user consent for installation; actual execution also depends on the runtime's tool permissions.
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