Security audit
Security checks for vulnerabilities and agentic risk
The Beeminder actions have approval safeguards, but setup can execute unverified remote code and introduce broader agent changes without separate approval.
Review and approve CLI installation separately before allowing setup. Prefer a reviewed, version-pinned installation and disable automatic bundled-skill synchronization unless wanted. Connecting Beeminder entrusts its API key and requested operations to OOMOL. Data changes have explicit approval safeguards, but the downloaded installers and hosted connector were not verified by this artifact review.
The supplied command performs remote script execution for an apparent Oomol CLI installation and contains no Beeminder operations. Nothing in the supplied content establishes this installer as a supporting dependency for Beeminder management. The downloaded script's contents and subsequent effects are not available for inspection.
Piping a mutable remote installer directly into bash executes its contents with the agent process's privileges, without verifying a pinned artifact or reviewing it before execution. HTTPS protects transport but does not prevent a compromised hosting service or release pipeline from serving code that steals accessible credentials or modifies local files; the installation prerequisite explains the download but does not eliminate 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 setup directs the agent to execute remotely downloaded shell or PowerShell code without an explicit installation approval step or integrity verification. A Beeminder data request could therefore trigger arbitrary code execution and local system changes beyond the user's requested operation; the missing-CLI condition limits exposure but does not establish consent.
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
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## Resources
- Beeminder homepage: https://www.beeminder.com
- API documentation: https://api.beeminder.com/