Security audit
Security checks for vulnerabilities and agentic risk
The Vectera actions have clear safeguards, but setup can run unverified software and change other agents’ installed skills without clear approval.
Review local setup before proceeding. Install a reviewed CLI release yourself, consider disabling its automatic skill synchronization, and connect only the intended Vectera account. Keep the existing confirmation requirement for meeting-room and access changes. The remote installer’s exact behavior remains unverified; no malicious payload was established.
The supplied code runs an Oomol installer rather than performing any visible Vectera operation. Although installation can be a supporting implementation detail, nothing supplied establishes this installer as a dependency of the declared Vectera functionality. The downloaded script's contents and further effects are not shown.
Piping an unpinned HTTPS download directly into Bash executes whatever the installation endpoint returns with the invoking user's privileges, without a separate verification step. Compromise of the distribution endpoint could therefore enable local data theft or modification; the legitimate CLI dependency and missing-tool condition do not eliminate this supply-chain risk.
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 setup instructions direct execution of downloaded shell and PowerShell scripts without explaining that they run remote code or requiring explicit installation approval. Restricting setup to a missing-CLI error reduces exposure, but a routine Vectera request can still lead to security-sensitive local changes without informed consent.
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