Security audit
Security checks for vulnerabilities and agentic risk
The Glyphic reads fit the skill’s purpose, but setup directs the agent to execute unverified remote installers without separate user approval.
Review and approve CLI installation separately before allowing the fallback to run. Prefer a verified, fixed release, and review or disable the CLI’s automatic agent-skill synchronization. Connecting Glyphic permits OOMOL-mediated access to call content. The remote installer contents remain unverified; no malicious behavior was established in the bundled artifact.
The supplied code installs software from an unrelated service rather than performing the declared Glyphic data operations. Nothing in the supplied content establishes this installer as a supporting dependency for Glyphic. The downloaded script is not supplied, so its additional behavior cannot be determined.
Piping an HTTPS response directly into Bash executes mutable remote code without checking a pinned version, signature, or independently trusted digest; the PowerShell alternative has the same issue. Compromise of the installer endpoint or distribution infrastructure could result in arbitrary code execution with the user's permissions, despite the legitimate dependency-installation purpose.
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 execute downloaded installers without explicit approval for local software installation or disclosure of potential system changes. Although conditional and relevant to the workflow, this expands a read-only Glyphic request into execution of installation code with the invoking user's permissions.
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