Security audit
Security checks for vulnerabilities and agentic risk
The CraftMyPDF workflow is clearly scoped, but its automatic setup executes unverified downloaded code and may install additional persistent agent skills.
Review and verify a fixed CLI release before allowing setup, and consider disabling its automatic skill synchronization. OOMOL will mediate access to your connected CraftMyPDF account. Confirm PDF payloads and hosted-output handling before execution. The remote installers and hosted implementation were not verified; no malicious behavior was established in the bundled file.
The supplied command performs remote software installation rather than any visible CraftMyPDF operation. Nothing in the supplied content establishes this installer as a supporting dependency for CraftMyPDF. The downloaded script's contents and further effects are not available for assessment.
Piping the HTTPS installer response directly into bash executes mutable external content without an integrity check or review opportunity. Although the endpoint is consistent with the documented CLI dependency, compromise of that endpoint or its delivery infrastructure could result in arbitrary code execution under the agent's account; this is the same underlying issue as 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
The setup instructions execute remotely retrieved shell or PowerShell code without a pinned version, independently verified integrity, or a user-approval checkpoint for installation. A compromised distribution endpoint could therefore execute arbitrary code with the agent process's privileges; limiting setup to a missing-CLI error reduces exposure but does not remove the risk.
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