Security audit
Security checks for vulnerabilities and agentic risk
The Ordinal reading features fit the stated purpose, but missing software can trigger unverified remote installation without a separate approval step.
Review and approve CLI installation separately before enabling this skill. Inspect a fixed installer or release, review its bundled-skill changes, and restrict the connected Ordinal account to the access you need. Ordinal requests pass through OOMOL and may incur usage charges. The remote installer contents and hosted connector behavior were not verified; the artifact does not establish malicious intent.
The supplied command installs software through a download-and-execute pipeline rather than performing the declared Ordinal operations. Nothing in the supplied chunk establishes this installation as a supporting dependency for Ordinal. The downloaded script's contents and further effects are not available for assessment.
Piping an HTTPS response directly into Bash executes mutable remote content without verifying a pinned version, checksum, or signature; the PowerShell example has the same trust problem. If the installer delivery infrastructure is compromised, attacker-controlled code could run with the agent process's permissions and access local files or credentials, 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 fallback directs the agent to execute downloaded shell or PowerShell code without explaining that this can modify the local system or requiring user approval for installation. Restricting setup to a missing-CLI error reduces exposure, but an Ordinal read request can still unexpectedly become a local software installation.
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