Security audit
Security checks for vulnerabilities and agentic risk
The TikHub workflow makes sense, but setup executes unverified remote code and the required CLI can install additional agent skills without this skill explaining that behavior.
Review the setup before installing. Prefer a vetted, pinned CLI installation and disable automatic skill synchronization with OO_SKILLS_SYNC_DISABLED=1 if you want only this integration. Use minimum TikHub scopes, protect account/key information, and monitor request charges. The exact remote installer and hosted connector behavior remain unverified; the artifacts do not establish malicious intent.
The supplied command performs remote script execution rather than TikHub search or data retrieval. Although installation can be a supporting implementation detail, the supplied chunk establishes no relationship between this installer and TikHub. The installer's contents and any further effects cannot be determined from this command alone.
The supplied chunk performs only a CLI login operation and does not identify TikHub or implement the declared data-access purpose. Authentication could support a TikHub integration, but no such connection is established here; login is the entire supplied behavior rather than a supporting step in a demonstrated TikHub workflow.
The fallback installation command pipes a remotely fetched, unpinned script directly into Bash without an independent integrity check; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint or its publishing pipeline could execute arbitrary code with the agent process's permissions, exposing accessible files and credentials. Its legitimate setup purpose and missing-CLI prerequisite limit exposure but do not remove the risk.
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
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