Security audit
Security checks for vulnerabilities and agentic risk
The Nusii workflow requires approval for account changes, but its setup fallback directs the agent to run an unverified remote installer without separate user approval.
Review the installation fallback before enabling this skill. Prefer a verified CLI release installed under your control, and require approval before either downloaded installer executes. OOMOL will mediate access to your Nusii data; check proposal changes and recipients when approving actions. The complete bundled skill was inspected, but remote installer and hosted connector behavior remain outside this review.
The supplied code performs remote software installation rather than the declared Nusii Proposals management. Although installing dependencies can be a supporting implementation detail, no connection between this installer and Nusii functionality is established here. The downloaded script's contents and additional effects cannot be determined from this chunk.
Piping a live remote script directly into Bash executes whatever the endpoint supplies with the invoking user's privileges, without version pinning or independent integrity verification. The URL belongs to the documented CLI provider and setup is conditional, which reduces suspicion of malicious intent but does not prevent host compromise if the distribution endpoint or installer is compromised; the PowerShell example has the same weakness.
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 an agent to execute remote installation scripts without explicitly obtaining approval for local code execution and system changes. Although installation is conditional on the CLI being absent, the write-confirmation rules cover Nusii state rather than host changes, leaving a separate authorization gap if the setup commands are permitted.
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