Security audit
Security checks for vulnerabilities and agentic risk
The Moesif integration is coherent, but its setup directs the agent to execute remote installers without clearly explaining their effects or requiring user approval.
Review is warranted for setup behavior, not evidence of malicious intent. Install the CLI through a separately reviewed process, check whether it installs or updates other agent skills, and authorize those changes explicitly. Confirm that OOMOL should mediate access to your Moesif account. The bundled skill was fully inspected, but external installer contents and resulting system changes remain unverified.
The supplied command executes an installer from an unrelated service, with no demonstrated connection to the declared Moesif functionality. This is a materially different operation rather than an evident supporting implementation detail. The remote script's contents are not supplied, so its further effects cannot be determined.
Piping an HTTPS response directly into bash executes whatever the installer endpoint supplies without a pinned version, integrity verification, or review. Compromise of the hosting or release infrastructure could therefore execute attacker-controlled code with the agent's user permissions; 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
The fallback instructs the agent to install software by executing a remote script without first explaining the system changes or obtaining installation-specific approval. Although limited to a missing dependency, this expands a read-oriented Moesif task into arbitrary code execution with the invoking user's permissions; the actual installer behavior is not provided for review.
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