Security audit
Security checks for vulnerabilities and agentic risk
The Bookingmood read functions fit the stated purpose, but setup can execute changing remote code and introduce broader agent changes without clear user approval.
Review setup before enabling this skill. Install a verified CLI version separately with your approval, check its automatic agent-skill installation settings, and authorize only the Bookingmood access you need. The remote installer and hosted connector implementation remain outside the inspected package; the artifacts do not establish malicious intent.
The supplied command performs remote installer execution, not Bookingmood searching or reading. Nothing in the supplied chunk establishes the installer as a supporting dependency for Bookingmood access. This adds an undeclared local execution and installation capability. The downloaded script's contents and any further effects cannot be determined from this chunk.
The supplied chunk performs authentication rather than searching or reading Bookingmood data. Authentication could be a supporting implementation detail, but nothing in this chunk connects the login to Bookingmood or implements the declared functionality.
Piping an HTTPS download directly into Bash executes mutable remote content without a pinned version, signature verification, or an inspection step. Compromise of the installer host or its delivery pipeline could therefore execute arbitrary code with the agent process's permissions; the Windows example has the same issue.
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 setup fallback instructs the agent to execute downloaded shell or PowerShell code without requiring informed approval for installation or local system changes. Although triggered only when the CLI is missing, this expands a read-only Bookingmood request into local code execution with the agent process's 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