Security audit
Security checks for vulnerabilities and agentic risk
The Webflow workflow has clear safeguards, but its setup instructions can run unverified downloaded code without asking you first.
Review and install the CLI separately before using this skill, and check whether its bundled-skill synchronization will affect other agents. Use narrowly scoped Webflow access and retain confirmation before publishing, editing, or deleting content. The remote installers were unavailable for inspection, so their exact behavior remains uncertain; the supplied artifact does not establish malicious intent.
The supplied command invokes an Oomol installer rather than performing Webflow operations. No Webflow integration or dependency relationship is shown that would establish this as a supporting implementation detail. The remote script's contents and subsequent behavior are not available in the supplied chunk.
The curl-to-bash command immediately executes mutable remote content without pinning a version or verifying its integrity; the PowerShell alternative has the same weakness. Compromise of the installer distribution infrastructure could execute attacker-controlled code with the agent process's local permissions, potentially exposing accessible files and credentials. HTTPS and the legitimate dependency context reduce some concerns but do not prevent 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 fallback directs the agent to install software by executing downloaded scripts without requiring explicit approval or explaining that this runs third-party code locally. Although limited to a missing-CLI error, it expands a Webflow task into a local software installation outside the skill's explicit confirmation rules for Webflow changes.
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