Security audit
Security checks for vulnerabilities and agentic risk
The Heartbeat features match the description, but automatic setup executes unverified remote code and warrants review.
Review and install a verified CLI separately before enabling this skill, and prevent automatic execution of its remote installer fallback. Review the CLI's agent-skill syncing behavior and connect only the intended Heartbeat account. No malicious behavior was established; the Review verdict concerns installation control and an uninspected external dependency.
The read-oriented skill conditionally instructs the agent to install a CLI by executing remotely fetched code, expanding its effects beyond reading Heartbeat data. Installing a documented dependency is not inherently deceptive, but executing an unverified installer without explicit approval creates a supply-chain code-execution risk; this overlaps with the SC2 finding.
The supplied chunk performs only a CLI login and contains no Heartbeat-specific operations or connection to the declared functionality. Authentication could support a Heartbeat integration, but that relationship is not established here; as supplied, the implementation has a materially different primary purpose.
The command pipes an unpinned remote installer directly into Bash, allowing the fetched script to execute with the agent process's privileges without integrity verification or review. HTTPS and the restriction to missing-CLI situations reduce exposure but do not prevent malicious code execution if the distribution endpoint is compromised; the PowerShell example has the same 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
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