Security audit
Security checks for vulnerabilities and agentic risk
The NinjaPear searches fit the stated purpose, but the automatic setup can execute unverified software without a clear approval step.
Review and install a verified CLI release separately before using this skill, and check its automatic skill-synchronization settings. Requests use your OOMOL-connected NinjaPear account and may consume service credit. The remote installers could not be inspected, so their exact local changes remain unknown. The Review verdict concerns setup control, not evidence of malicious intent.
The supplied chunk installs software from cli.oomol.com rather than searching or reading NinjaPear data. Nothing in the provided content establishes this installer as a supporting dependency for NinjaPear, so its remote-code execution is not accounted for by the declared purpose. The downloaded script's further behavior cannot be determined from this chunk.
Piping an HTTPS response directly into Bash executes mutable remote content without a separate integrity or authenticity check; the PowerShell alternative has the same weakness. A compromised distribution endpoint or malicious installer update could execute arbitrary code and access files or credentials available to the process, although the skill provides no evidence that such compromise has occurred.
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-CLI fallback instructs the agent to install software by immediately executing a remote script, without explaining the local-system effects or requiring user approval. Although conditional and relevant to the skill's dependency, this expands a data-reading request into 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