Security audit
Security checks for vulnerabilities and agentic risk
The NeetoDesk workflow is coherent, but its setup instructions can execute unverified downloaded software without a separate approval step.
Review and approve the CLI installation separately, preferably using a pinned release with independently verified integrity. Connect only the intended NeetoDesk account and retain the required confirmation before ticket changes or replies. The complete bundled artifact was inspected; remote installer behavior remains unverified, and no malicious intent was established.
The supplied code performs an Oomol installation rather than any demonstrated NeetoDesk operation. Dependency installation can be a supporting implementation detail, but nothing supplied establishes that this installer supports the declared purpose. The downloaded script's contents and further effects are not visible, so no specific downstream behavior can be confirmed.
Piping a mutable remote script directly into Bash executes its contents with the agent's local privileges without prior inspection or integrity verification. A compromised distribution endpoint could therefore expose local files or credentials and modify the system; HTTPS and the legitimate setup purpose reduce some risks but do not establish artifact integrity. The PowerShell download-and-execute example has the same underlying 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 missing-CLI recovery path instructs the agent to install software without explaining local changes or requiring user approval. Although installation is a legitimate prerequisite and only occurs after a specific error, authorization for NeetoDesk operations should not implicitly authorize downloaded code to modify the local environment.
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