Security audit
Security checks for vulnerabilities and agentic risk
The Demodesk reads fit the stated purpose, but the required CLI can persistently change other agent skills without the skill explaining that impact.
Review and deliberately install a trusted CLI release before use. Disable or explicitly approve its cross-agent skill synchronization, and connect only the intended Demodesk account. Requests use OOMOL as an intermediary. The sole bundled file was fully inspected; the external installers and exact installed CLI behavior remain unverified.
The declared purpose concerns accessing Demodesk data, but the supplied code executes an external installer. Although CLI installation could be a supporting implementation detail, this chunk establishes no relationship between that installer and Demodesk functionality. The remote script's contents are not supplied, so its further behavior cannot be assessed.
The command streams a remote installer directly into Bash, making the current contents served by the installation endpoint executable without prior inspection or authenticated version pinning. HTTPS protects transport but does not prevent a compromised vendor endpoint or release from delivering code that accesses local data or modifies the system; this is the same underlying installation risk identified by SQP-2.
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 downloaded shell or PowerShell code without an explicit approval step, integrity verification, or disclosure of potential system changes. Restricting this to a missing-CLI error reduces exposure, but a compromised installer could still execute arbitrary code with the invoking user'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