Security audit
Security checks for vulnerabilities and agentic risk
The Cin7 reading workflow fits its purpose, but setup can execute unverified remote code without a separate user approval step.
Review and install the CLI separately from a verified release before allowing this skill to run. Check its automatic agent-skill synchronization settings and confirm that routing Cin7 access through OOMOL is acceptable. The bundled reading instructions show no malicious behavior, but the remote installer and connector implementation remain unverified.
The supplied chunk performs remote installer execution and contains no Cin7 Core data-access functionality or evidence connecting the installer to that functionality. This is materially different from the declared purpose, not merely a demonstrated supporting implementation detail. The downloaded script's contents and further effects cannot be determined from this chunk.
The command streams a mutable remote script directly into Bash without version pinning or independent integrity verification; the PowerShell alternative has the same weakness. A compromised distribution endpoint could execute arbitrary code with the agent's local permissions, potentially exposing accessible files and credentials, even though the installation source appears relevant and no malicious payload is shown.
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
On a missing-command error, the skill directs the agent to install software without requiring approval for local system changes or explaining the installer's privileges and effects. Although this is a conditional prerequisite rather than the normal read workflow, it expands a data-reading request into execution of remote code with the invoking user's permissions.
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