Security audit
Security checks for vulnerabilities and agentic risk
The Yuan Dian integration is coherent, but its automatic setup executes an unverified remote installer without clear user control.
Review and install the CLI yourself before enabling this skill, and prevent automatic execution of its download-and-run fallback. Review the CLI's bundled-skill installation behavior and limit it to intended agent hosts. Queries and submitted legal text pass through OOMOL to Yuan Dian, so avoid unnecessary confidential information. The remote installer and CLI implementation were not verified.
The supplied code installs software rather than searching or reading Yuan Dian data. Nothing in the chunk establishes that this installation is a supporting requirement for Yuan Dian access. The remote script's contents are not supplied, so its further behavior cannot be determined.
The fallback pipes a remotely fetched, unpinned script directly into Bash; the PowerShell alternative uses the equivalent download-and-execute pattern. If the installer endpoint or its delivery infrastructure is compromised, attacker-controlled code could run with the agent process's permissions and access local files or credentials. Restricting installation to a missing-CLI error reduces frequency but does not verify the script or obtain explicit installation approval.
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 workflow instructs the agent to submit action payloads through the OOMOL-connected Yuan Dian service, potentially including user-provided legal text and search queries. Although the service integration is disclosed, there is no warning about transmitting potentially sensitive content, and line 66 broadly labels read actions safe to run directly.
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