Security audit
Security checks for vulnerabilities and agentic risk
The Torii features fit the stated purpose, but setup instructs the agent to execute downloaded code without requiring separate approval.
Review the setup behavior before installing. Use a separately reviewed CLI installation, decide whether automatic installation and synchronization of other agent skills is acceptable, and grant only the Torii access needed. The downloaded installers and live connector implementation remain unverified.
The description presents a Torii data-access skill, but the supplied code executes an Oomol-hosted installer. Nothing in the chunk establishes that this installation supports Torii access, so it cannot be treated as a demonstrated supporting implementation detail. The remote script's contents are unavailable, so its specific effects cannot be determined.
The curl-to-bash pipeline immediately executes mutable remote content without a pinned version or independent integrity verification; the PowerShell alternative has the same weakness. HTTPS protects transport but does not protect against compromise of the distribution service or installer supply chain. Exploitation could execute arbitrary code with the agent process's permissions, although the file provides no evidence that the current installer is 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 fallback directs the agent to execute downloaded shell or PowerShell code without requiring informed approval for local installation. A request to read Torii data does not inherently authorize arbitrary local code execution, and a compromised installer could access files and credentials available to the executing account. Limiting this to a missing-CLI error reduces exposure but does not resolve the authorization gap.
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