Security audit
Security checks for vulnerabilities and agentic risk
The Simla workflow has clear safeguards, but its setup can execute unverified remote installers without a separate approval step.
Review the CLI installation separately before allowing setup to run. Prefer a verified, pinned release and inspect its agent-skill synchronization settings. OOMOL will mediate access to your Simla records; retain the skill's confirmation requirements for changes. Both remote installer retrieval attempts failed, so their contents remain unreviewed.
The supplied code performs remote software installation rather than the declared Simla.com data operations. Although dependency installation can be a supporting implementation detail, this chunk provides no evidence connecting the Oomol installer to the declared purpose. The downloaded script's contents are not supplied, so its further behavior cannot be determined.
Piping a mutable remote script directly into Bash executes its contents with the agent's local privileges without integrity verification or an opportunity for prior inspection. Compromise of the distribution endpoint could enable credential theft or local file modification; HTTPS and the legitimate CLI prerequisite reduce some risks but do not prevent supply-chain compromise. The PowerShell installation command has the same weakness, and this finding overlaps 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
When the CLI is missing, the skill directs the agent to execute an external installer without explicit user approval or disclosure of local system changes. This crosses from the requested CRM operation into local code execution; the conditional setup reduces exposure but does not establish consent or 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