Security audit
Security checks for vulnerabilities and agentic risk
The Octopus data-reading workflow is coherent, but its setup fallback executes unverified remote installers without a separate approval step.
Require separate approval before setup and review a fixed CLI release, including any changes to installed agent skills. Use a read-only Octopus API key and consider OOMOL's role in handling account credentials and deployment data. The remote installer and live connector implementation were not verified; the reviewed artifact does not establish malicious behavior.
The supplied command executes a remote installer rather than searching or reading Octopus Deploy data. No connection to the declared Octopus Deploy functionality is shown, so this is an undeclared capability and inconsistent resource access, not an established supporting implementation detail. The contents and additional effects of the downloaded script are not available for assessment.
Piping a remotely fetched script directly into Bash executes its contents with the agent process's privileges without verifying a pinned version, signature, or trusted digest; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint or release pipeline could therefore expose local files and credentials or modify the host, although no malicious installer content 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 instructs the agent to install software without explicitly obtaining approval for local system changes or explaining that downloaded code will execute. A request to read deployment data does not inherently authorize software installation, although the conditional setup path limits exposure.
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