Security audit
Security checks for vulnerabilities and agentic risk
The Klipfolio reads match the stated purpose, but automatic setup runs unverified remote installers without a separate user decision.
Review and approve CLI setup separately before allowing the agent to execute it. Verify the installer, use a Klipfolio connection limited to needed reads, and consider disabling the CLI's skill synchronization. Remote installer effects remain unverified; the artifact does not establish malicious behavior.
The declared purpose describes Klipfolio data access, but the supplied code runs a remote installer from a different service. No visible evidence connects this installation to the declared functionality, so it is an undeclared capability rather than an established supporting implementation detail. The downloaded script's contents and further effects are not available for assessment.
The curl-to-bash pipeline immediately executes whatever script the remote endpoint supplies, without a pinned version or independent integrity verification. A compromised installer host or distribution pipeline could execute arbitrary code with the agent process's permissions, potentially exposing local files and credentials; the PowerShell example has the same weakness.
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
When the CLI is missing, the skill directs installation without explaining that it executes remote code and modifies the local environment, or requiring explicit approval. The missing-command condition limits exposure, and strict enforcement of the declared Bash(oo *) restriction should block these installer commands, but neither makes this a safe setup instruction.
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