Security audit
Security checks for vulnerabilities and agentic risk
The conversion workflow fits its purpose, but automatic setup can introduce persistent changes to other agent skills without clearly explaining them.
Review the CLI installation and disable automatic skill synchronization if you want only document conversion. Submit confidential links only when you authorize OOMOL and Docsend2pdf to access them. The remote installer contents and hosted processing remain unverified.
The declared purpose concerns accessing Docsend2pdf data, but the supplied code runs an installer from a different service. Nothing in the supplied chunk establishes that this installation supports the declared functionality. The downloaded script's contents are not provided, so its further behavior cannot be assessed.
The setup command executes a remotely fetched, mutable script directly in a shell without inspection, version pinning, or independent integrity verification. Compromise of the distribution endpoint could execute attacker-controlled code with the agent process's permissions; the missing-CLI prerequisite limits exposure but does not mitigate execution risk, and the PowerShell alternative has the same issue.
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
DocSend URLs can contain access-bearing identifiers or lead to confidential documents; sending them through OOMOL to a conversion provider exposes them outside the original document-sharing context. The skill openly names these services, reducing the likelihood of deceptive exfiltration, but its blanket treatment of untagged actions as safe reads does not account for this sensitive-data transfer.
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