Setup downloads and executes a third-party npm CLI
Source references: 2The instructions recommend either a global installation or immediate download and execution of `@runcomfy/cli` using `npx -y`. No version or package integrity value is pinned, so the code supplied by the registry at that time is executed.
If the package, publisher account, or a dependency is compromised, installation code can run with the user's permissions. A global install also makes a lasting change to the user's Node.js tool environment.
The documentation offers an unpinned global npm install and an auto-confirming npx invocation; both trust the package code served by npm at that time. They are described as one-time operator setup rather than commands automatically run for every generation, but following them still executes third-party code locally. Users can request a pinned version and integrity information.
```bash# 1. Install (one of — see runcomfy-cli skill for details)npm i -g @runcomfy/cli # global installnpx -y @runcomfy/cli --version # zero-install# 2. Sign in (interactive — opens browser)runcomfy login# or in CI / containers:export RUNCOMFY_TOKEN=<token-from-runcomfy.com/profile>Show 1 other places
- **Generated-file size cap**: the CLI aborts any single download > 2 GiB.- **Scope of bash usage**: declared `allowed-tools: Bash(runcomfy *)`. The skill never instructs the agent to run anything other than `runcomfy <subcommand>` — `npm` / `npx` / `export RUNCOMFY_TOKEN=...` lines are one-time setup for the operator, not commands the skill executes on each call.