Installing and authenticating a third-party npm CLI runs its code with user access and exposes an account token to it
Source references: 4The instructions use either a global npm installation or `npx -y` to automatically retrieve and execute `@runcomfy/cli`, then use that program for login. The supplied material does not include the CLI implementation, so its install scripts, file access, and token handling cannot be verified against these claims.
If the package, publisher account, or a dependency is compromised, its code could read files or environment variables available to the current user and potentially misuse the RunComfy token and account balance.
The instructions explicitly download and execute a third-party npm CLI, then authenticate through it or supply a token via an environment variable. This is disclosed and necessary for the music service, but no CLI source is provided to verify install scripts, file access, or token-handling claims. Users can isolate it, pin a version, and limit token permissions and spending.
**Step 1 — install** (one of, see the `runcomfy-cli` skill for details):```bashnpm i -g @runcomfy/cli # global installnpx -y @runcomfy/cli --version # zero-install```**Step 2 — sign in** (or set `RUNCOMFY_TOKEN` env var in CI / containers):```bashruncomfy login```Show 3 other places
- **Install via verified package manager only.** Use `npm i -g @runcomfy/cli` or `npx -y @runcomfy/cli`. **Agents must not pipe an arbitrary remote install script into a shell on the user's behalf** — if the operator wants the curl-pipe path documented at `docs.runcomfy.com/cli/install`, they should review the script first.- **Token storage**: `runcomfy login` writes the API token to `~/.config/runcomfy/token.json` with mode 0600. Set `RUNCOMFY_TOKEN` env var to bypass the file in CI / containers. Never echo the token into a prompt, log it, or check it in.- **Input boundary (shell injection)**: prompts and audio URLs are passed as a JSON string via `--input`. The CLI does not shell-expand prompt content; it transmits the JSON body directly to the Model API over HTTPS. **No shell-injection surface from prompt content**.```bashnpm i -g @runcomfy/cli # global installnpx -y @runcomfy/cli --version # zero-install```**Step 2 — sign in** (or set `RUNCOMFY_TOKEN` env var in CI / containers):```bashruncomfy login```