Security audit
Security checks for vulnerabilities and agentic risk
The BoldSign workflow is coherent, but setup executes unverified remote installers without clear approval and omits broader changes the CLI can make to agent skills.
Review and approve CLI installation separately before allowing setup. Prefer a pinned, verified release, and review or disable automatic skill synchronization across your agents. OOMOL mediates access to your connected BoldSign account. The complete bundled artifact was inspected, but the remote installers and exact installed runtime were not verified.
The supplied command performs remote script execution rather than any visible BoldSign operation. Nothing in the supplied chunk establishes that the Oomol installer is a supporting dependency for BoldSign, making its installation materially inconsistent with the declared purpose. The downloaded script's further behavior cannot be determined from this chunk.
Piping an HTTPS response directly into Bash executes mutable remote code without a pinned version or independent integrity verification. Compromise of the installer endpoint or release infrastructure could execute attacker-controlled code with the agent process's privileges; the legitimate OOMOL dependency and missing-CLI condition narrow exposure but do not remove 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 missing-CLI fallback directs the agent to execute an installer without first explaining local code execution or requesting approval for system changes. Although installation is a legitimate prerequisite, authorization to perform a BoldSign task does not necessarily authorize installing software; this fallback can cross that boundary if the Bash permission layer permits it.
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