Security audit
Security checks for vulnerabilities and agentic risk
Gotify operations are appropriately controlled, but setup permits remote code execution and leaves broader agent changes undisclosed.
Review setup before enabling this skill. Prefer a reviewed, pinned CLI installation and confirm which agent skills it will install or update. Upstream documents OO_SKILLS_SYNC_DISABLED for disabling startup skill synchronization in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Understand that OOMOL mediates Gotify access. The remote installers remain unverified; no malicious behavior was established in the bundled artifact.
The supplied code installs software from an Oomol endpoint rather than performing Gotify operations. No visible code establishes that this installation supports the declared Gotify functionality. The remote installer's contents are not supplied, so its further behavior cannot be assessed.
Piping an unpinned HTTPS response directly into bash executes the remote endpoint's current contents without prior inspection or integrity verification. Compromise of the installer hosting or release pipeline could therefore lead to arbitrary code execution with the agent's local permissions; the PowerShell alternative has the same trust weakness.
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 directs the agent to execute remote installation scripts without first explaining local changes or requiring explicit installation approval. Although dependency installation is relevant to the skill, it can modify the user's environment and execute code with the agent's local permissions; the Gotify write-confirmation rules do not explicitly cover this setup operation.
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