Security audit
Security checks for vulnerabilities and agentic risk
The Clockify integration is coherent, but its setup can execute changing remote code without clearly requiring your approval.
Review and approve CLI installation separately, preferably using a pinned, verified release. Check its effects on other installed agent skills before first use. OOMOL will mediate access to your connected Clockify account; retain the skill's explicit confirmations for changes and deletions. The installer and hosted connector implementations were not available in this artifact, so their full behavior remains unverified.
The supplied chunk runs a third-party installer rather than performing any demonstrated Clockify operation. Nothing provided establishes that this installer is a supporting dependency for Clockify functionality. The downloaded script's contents are unavailable, so its further effects cannot be determined.
The command pipes a mutable remote script directly into Bash without version pinning or integrity verification; the PowerShell alternative uses the same download-and-execute pattern. Compromise of the installer distribution infrastructure could therefore lead to arbitrary code execution with the invoking user's privileges, although the file provides no evidence that the installer is currently malicious.
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 the agent to execute a remote installer without explaining local system changes or requiring explicit installation approval. Although conditional setup reduces exposure, installing software crosses a different trust boundary from operating Clockify and can execute code with the invoking user's privileges.
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