Security audit
Security checks for vulnerabilities and agentic risk
The Orimon workflow fits its purpose, but setup executes unverified remote installers and leaves broader changes to agent skills unexplained.
Review setup before installing. Prefer a separately reviewed, pinned CLI installation, and decide whether it may install or refresh other agent skills. Upstream documents OO_SKILLS_SYNC_DISABLED for disabling startup skill synchronization. Messages and connected-account access pass through OOMOL, so use only data appropriate for that service. The remote installers could not be inspected; their local effects remain uncertain.
The supplied code only runs an external installer; it contains no Orimon integration or data operations. Installing a dependency could be a supporting implementation detail, but the supplied content establishes no relationship between this Oomol installer and the declared Orimon purpose. The downloaded script's contents and further effects are not visible.
Piping a mutable remote installer directly into bash executes its contents without independent integrity verification or inspection. Compromise of the distribution endpoint or its publishing pipeline could execute arbitrary code with the agent process's permissions; HTTPS and the legitimate dependency relationship 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
When the CLI is missing, the skill directs the agent to install software by executing a remote script without first requesting approval or explaining local changes. Although limited to first-time setup, this expands authorization for an Orimon task into local code execution with the agent process'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