Security audit
Security checks for vulnerabilities and agentic risk
The notification features fit the stated purpose, but automatic setup executes unverified downloads and can introduce broader agent changes.
Review the CLI installation before allowing automatic setup, including its changes to other agents' skills. The publisher documents OO_SKILLS_SYNC_DISABLED for disabling startup skill synchronization in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). OOMOL mediates notification requests and connected credentials. Confirm the destination and message before publishing. The downloaded installers and remote service implementation were not inspected; no malicious behavior was established.
The supplied command executes an installer hosted on cli.oomol.com. Nothing in the chunk performs ntfy operations or establishes that this installation supports them. Its observable purpose and accessed resource therefore differ materially from the declared ntfy functionality. The installer's additional effects cannot be determined from this chunk.
The supplied chunk performs only an authentication command, rather than the declared ntfy data operations. Authentication could be a supporting implementation detail, but nothing in this chunk connects the oo login to ntfy or establishes it as a prerequisite.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Available actions
- `get_account` — Retrieve ntfy account profile, limits, and usage for the access token.
- `publish_message` — Publish a notification message to a ntfy topic. [write]
## Safety
Piping a remotely fetched installer directly into bash executes its contents without prior inspection or independent integrity verification. HTTPS protects transport but does not protect against compromise of the distribution service; the conditional setup context reduces exposure frequency but not the potential impact.
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 instructs the agent to execute downloaded shell or PowerShell code without an explicit installation approval step or independent integrity verification. Although this is legitimate dependency setup and only runs when the CLI is missing, a compromised distribution endpoint could execute arbitrary code with the invoking user's privileges; the substantive issue is execution control, not merely the missing warning.
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