Security audit
Security checks for vulnerabilities and agentic risk
The Float reads are appropriately scoped, but setup executes an unpinned remote installer without clear approval for its broader local changes.
Review setup before enabling this skill. Prefer installing a pinned, verified CLI separately, review its bundled agent-skill changes, and connect only the intended Float account. The supplied instructions show no malicious intent, but they do not adequately bound installation effects. Remote installer and hosted connector behavior remain unverified.
The supplied command performs remote software installation rather than searching or reading Float data. Although installation can be a supporting implementation detail, the supplied chunk establishes no relationship between this Oomol installer and the declared Float functionality. The contents and further effects of the downloaded script are not visible and cannot be assessed.
Piping an HTTPS response directly into bash executes mutable remote content without pinning or independent integrity verification; the PowerShell alternative has the same weakness. A compromised installer endpoint or release pipeline could execute attacker-controlled code with the agent's local privileges, although no such compromise is demonstrated here.
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 missing-CLI fallback directs the agent to execute a remote installer without requiring user approval for local system changes. Although conditional and relevant to setup, this can turn a read-only Float request into installation and arbitrary code execution with the agent's local privileges.
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