Security audit
Security checks for vulnerabilities and agentic risk
The SignWell workflow is coherent, but automatic software installation and undisclosed changes to other agent skills warrant review.
Review and approve CLI setup separately before allowing the automatic fallback. OOMOL will mediate access to your SignWell account and document data. Prefer a reviewed CLI version, retain confirmation for document changes and sending, and consider the documented OO_SKILLS_SYNC_DISABLED setting to prevent startup skill synchronization. The bundle contains only instructions; installer and backend behavior remain unverified.
The supplied code performs remote installation rather than any visible SignWell operation. Dependency installation can be a supporting implementation detail, but the supplied material does not establish that this installer supports the declared SignWell functionality. The downloaded script's contents and any further effects are not available for assessment.
The command pipes a remotely retrieved, unpinned script directly into Bash; the PowerShell alternative similarly executes downloaded content immediately. If the installer distribution infrastructure is compromised, attacker-controlled code could execute with the agent process's local permissions and access available files or credentials; HTTPS alone does not establish artifact integrity.
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 fallback instructs the agent to install software without explaining local system changes or requesting approval. Although installation is conditional and relevant to the task, permission to operate SignWell does not necessarily authorize executing an installer or modifying 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