Security audit
Security checks for vulnerabilities and agentic risk
Certificate operations are clearly scoped, but setup can execute unverified downloaded code without a separate approval step.
Review and approve a verified CLI installation before allowing setup to run, including any automatic installation of additional agent skills. OOMOL will mediate access to certificate data. Keep the required approvals for creation and deletion. The remote installer contents could not be inspected; no malicious intent was established.
The supplied code performs remote script execution and shows no Accredible integration or certificate data operations. Nothing in the supplied content establishes this installer as a supporting dependency for the declared purpose. The downloaded script's contents and any further effects are not available for assessment.
Piping a remotely fetched script directly into Bash executes mutable network-delivered code without verifying its contents, signature, or expected digest. Compromise of the installer distribution infrastructure could lead to arbitrary code execution, local credential theft, or file modification; HTTPS and the legitimate dependency context do not eliminate this supply-chain risk.
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 directs the agent to execute downloaded shell or PowerShell code without requiring user approval for local software installation or explaining the resulting system changes. A missing CLI can therefore escalate an ordinary certificate-management request into execution of externally controlled code with the agent's local privileges, although the error-triggered setup 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