Security audit
Security checks for vulnerabilities and agentic risk
The UnifAPI workflow is coherent, but setup directs the agent to execute unverified downloaded software without a clear installation approval step.
Review and install the CLI separately before allowing this skill to run. Check its automatic skill synchronization and disable it if unwanted using the publisher's documented controls. Keep the skill's confirmations for data changes. The remote installers and downloaded CLI were not audited; the evidence supports setup and persistence concerns, not a finding of malicious intent.
The supplied code performs remote script installation rather than the declared UnifAPI data operations. Although installing a dependency could be a supporting implementation detail, nothing supplied establishes that this Oomol installer supports UnifAPI. The downloaded script's contents and any further behavior are unknown.
Piping a remote installer directly into Bash executes whatever the endpoint returns with the agent process's local privileges, without inspecting the script or verifying a pinned artifact. Compromise of the distribution endpoint could therefore expose accessible files and credentials or modify the environment; the PowerShell alternative has the same risk. The domain is relevant to the documented CLI and installation is conditional, but neither establishes artifact integrity.
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 install software when the CLI is missing without first explaining local system changes or obtaining explicit installation approval. A request to access UnifAPI does not necessarily authorize modifying the local environment, although the conditional setup path limits exposure.
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