Security audit
Security checks for vulnerabilities and agentic risk
The Ably operations have approval safeguards, but setup executes unverified remote code and leaves additional agent-skill installation behavior unexplained.
Review the CLI installation before allowing setup to run. Choose and verify a CLI release yourself, and consider setting OO_SKILLS_SYNC_DISABLED=1 before invocation to prevent automatic agent-skill changes. Use narrowly scoped Ably credentials and protect returned key data. The remote installer and hosted connector implementation were not inspected, so their exact behavior remains uncertain.
The supplied command performs remote software installation rather than the declared Ably Control data operations. Nothing in the supplied chunk establishes that this installer supports the stated purpose. The downloaded script's contents and further effects are not visible.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `delete_queue` — Delete an Ably queue by queue ID. [destructive]
- `get_account_stats` — Retrieve account-level Ably statistics for the connected account or account ID.
- `get_app_stats` — Retrieve app-level Ably statistics for an Ably app.
- `get_current_account` — Retrieve the Ably Control API token, user, and account associated with the access token.
- `list_apps` — List Ably apps in the connected account or supplied account ID.
- `list_keys` — List API keys for an Ably app.
- `list_queues` — List queues for an Ably app.
The setup instructions pipe a mutable remote script directly into Bash, and the Windows alternative similarly executes downloaded content without integrity verification. Although this is relevant dependency setup and only triggered when the CLI is missing, compromise of the installer distribution could execute arbitrary code with the agent's local privileges.
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