Setup downloads and executes an unpinned third-party npm package
Source references: 3`npm i -g` persistently changes the user's Node.js environment, while `npx -y` fetches and runs the package version resolved at that time without prompting. The supplied Skill does not pin an exact version.
If the package, publisher account, or a later release is compromised, installation code could read or modify files and credentials available to the current user. A global install may also affect other Node.js tooling.
The skill explicitly recommends installing an unpinned `@runcomfy/cli` release. A global install changes the user's Node.js environment, while `npx -y` downloads and executes the currently resolved release without confirmation. A compromised registry package, publisher account, or later release could therefore run code with the user's permissions. The “verified package manager” warning avoids arbitrary shell installers but does not address unpinned third-party execution. The user can ask for a pinned, verified version or restrict execution to an isolated environment.
```bash# 1. Install (see runcomfy-cli skill for details)npm i -g @runcomfy/cli # or: npx -y @runcomfy/cli --version# 2. Sign inruncomfy login # or in CI: export RUNCOMFY_TOKEN=<token>Show 2 other places
```bash# 1. Install (see runcomfy-cli skill for details)npm i -g @runcomfy/cli # or: npx -y @runcomfy/cli --version# 2. Sign inruncomfy login # or in CI: export RUNCOMFY_TOKEN=<token>- **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**.- **Token storage**: `runcomfy login` writes the API token to `~/.config/runcomfy/token.json` with mode 0600. Set `RUNCOMFY_TOKEN` env var in CI / containers.