Security audit
Security checks for vulnerabilities and agentic risk
The Trent workflow is coherent, but its automatic setup can execute unverified installers and introduce persistent changes to agent skills without clear user control.
Review the CLI setup before enabling this skill. Prefer a verified, preinstalled CLI and explicitly approve installation changes. The CLI documents OO_SKILLS_SYNC_DISABLED=1 to prevent startup skill synchronization. Confirm each chat payload, which passes through OOMOL to Trent. The remote installer contents remain unverified; no malicious payload was established.
The supplied code performs remote installer execution rather than any Trent data operation. Nothing in the chunk establishes that installing the Oomol CLI supports the declared Trent functionality. The downloaded script's contents and any further effects are not visible.
The command pipes a remotely retrieved, unpinned script directly into Bash, allowing its contents to execute with the agent's local privileges without prior inspection or integrity verification. A compromised distribution endpoint or installer could therefore access local data or alter the system; the Windows fallback has the same download-and-execute weakness, although neither endpoint is demonstrated to be malicious.
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-command fallback directs the agent to install software through downloaded shell or PowerShell scripts without separately obtaining approval for local system changes. Its conditional nature limits exposure, and tool permissions may block execution, but a request to operate Trent does not itself authorize installing software.
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