Security audit
Security checks for vulnerabilities and agentic risk
The Attention integration is clearly scoped, but its setup instructions can execute unreviewed remote software without a clear approval step.
Review and approve the CLI installation separately, preferably using a reviewed fixed release. Check its agent-skill synchronization behavior before first use. Connect only the intended Attention account and understand that OOMOL brokers access to its data. The remote installers and connector implementation were not verified; no installer was executed. The artifacts support a setup-control concern, not a finding of malicious intent.
The supplied chunk performs remote installation, not Attention data operations. Nothing in the provided code establishes that this installation supports the declared purpose, so it represents an undeclared capability and inconsistent resource access. The downloaded script's contents and further effects are not available for assessment.
Piping a remote script directly into bash executes whatever the endpoint supplies without review, version pinning, or independent integrity verification. Compromise of the distribution endpoint could lead to arbitrary code execution and exposure of files or credentials accessible to the process; HTTPS alone does not protect against a compromised publisher.
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 download and immediately execute third-party installation code without explicitly obtaining approval for local system changes. Although installation is a legitimate prerequisite and only occurs on a matching failure, the workflow expands a service-data task into local code execution with the agent's permissions.
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