Security audit
Security checks for vulnerabilities and agentic risk
The Deck.co workflow has clear controls, but its setup can execute unverified downloaded code without separate approval.
Review and install a fixed, verified CLI release yourself before using the skill. Consider disabling its automatic skill synchronization. OOMOL will mediate your Deck.co requests and credentials; confirm the connected account and each proposed write. The bundled instructions were fully reviewed, but the downloaded installers and hosted implementation remain unverified.
The supplied code performs remote installer execution rather than any visible Deck.co operation. Dependency installation can be a supporting implementation detail, but this chunk provides no evidence that the Oomol installer supports the declared Deck.co functionality. The downloaded script's contents and further effects cannot be determined from the supplied code.
The curl-to-bash command immediately executes whatever script the remote endpoint returns, without version pinning or independent integrity verification. HTTPS protects transport but not against a compromised trusted host or malicious installer update, which could access local files and credentials with the executing user's permissions; 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 requiring user approval or verifying a fixed, authenticated release. A compromised installer endpoint or publishing pipeline could execute arbitrary code with the agent's local privileges; restricting this behavior to a missing-CLI error reduces exposure but does not establish installer integrity.
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