Security audit
Security checks for vulnerabilities and agentic risk
The AroFlo workflow fits its purpose, but missing the required CLI triggers downloaded code execution without a separate installation approval step.
Review and approve the CLI installation separately before allowing fallback setup. Prefer a verified, fixed release and check whether it installs additional agent skills. Connecting AroFlo entrusts its credentials and requested business data to OOMOL. The downloaded installer and hosted connector implementation were not verified; no malicious behavior was established.
The supplied code installs software from an Oomol endpoint; it does not visibly search or read AroFlo data. No connection establishes this installer as a supporting requirement for AroFlo access. The downloaded script's contents are not supplied, so its further effects cannot be determined.
Piping a mutable HTTPS response directly into Bash executes remote code without a pinned version or independently verified integrity; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint or release pipeline could result in arbitrary code execution with the user's privileges, including theft of accessible credentials and files, despite the AroFlo actions themselves being read-only.
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 an agent to execute downloaded installation scripts without explaining that this runs third-party code with the invoking user's privileges or requesting installation-specific approval. Restricting this to a missing CLI reduces exposure, but an AroFlo read request should not implicitly authorize system 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