Security audit
Security checks for vulnerabilities and agentic risk
The HigherGov searches are appropriately scoped, but setup can execute unverified remote installers without clear user approval.
Review and approve CLI installation separately before using this skill, including which agent hosts receive bundled skills. HigherGov requests pass through OOMOL using your connected account. The sole bundled artifact was fully inspected, but remote installers and server-side behavior remain unverified; no evidence of intentional malicious behavior was found.
The supplied command executes an external installer and contains no HigherGov search or data-reading functionality. The declared purpose does not disclose installation or remote script execution, and the supplied code establishes no connection between this installer and HigherGov functionality. The downloaded script's contents and further effects are not shown.
Piping an HTTPS response directly into bash executes mutable remote content without a pinned version or independent integrity verification; the PowerShell example has the same weakness. Compromise of the installer hosting or release infrastructure could yield arbitrary code execution with the agent's local permissions, potentially exposing files and credentials, though the missing-CLI condition limits exposure.
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 directs the agent to execute downloaded shell or PowerShell code without explaining the system changes or requiring approval for installation. Although limited to missing-CLI situations, this expands a read-oriented data task into local software installation, with potential execution of attacker-controlled code if the installer distribution is compromised.
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