Security audit
Security checks for vulnerabilities and agentic risk
Formcarry changes require approval, but automatic CLI setup can execute changing remote code and introduce broader, undisclosed agent changes.
Review and install the CLI separately before enabling this skill, including its automatic bundled-skill synchronization. Confirm that OOMOL may access the intended Formcarry account and submissions. Form creation and deletion have clear approval requirements; the unresolved concern is setup and its broader local effects, not evidence of malicious intent.
The supplied code performs remote installer execution, not Formcarry operations. Nothing in the chunk establishes that installing the Oomol CLI is a supporting requirement for Formcarry access. The downloaded script's contents are not supplied, so its further behavior cannot be assessed.
Piping a mutable remote installer directly into bash executes its contents without prior inspection, version pinning, or independent integrity verification. HTTPS protects transport but does not prevent a compromised publishing account or distribution service from supplying code that can access local data and credentials; the conditional setup path limits exposure but does not remove this 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 fallback instructs installation through immediate execution of downloaded shell or PowerShell scripts without explaining the trust implications or requiring installation-specific approval. Although conditional on the CLI being missing, this can turn a routine Formcarry request into execution of unreviewed code with the invoking user's privileges.
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