install

A command for installing ComfyUI custom node packs, which add extra nodes to the ComfyUI visual workflow application.

In plain words
What is it for?
Installing a node pack from the ComfyUI registry or a GitHub repository.
Why use it?
It guides the agent through finding a pack, checking its details, asking for confirmation, and installing it.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/sandyup/comfyui-mcp/install
Clone the repo
git clone --depth 1 https://github.com/sandyup/comfyui-mcp
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 801 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.00801
Opus 5 $0.00004 $0.00400
Sonnet 5 $0.00002 $0.00160
Haiku 4.5 $0.00001 $0.00080

Measured yesterday against content hash dd20b636ade5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

install scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugin/commands/install.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/comfy-install — Install a Custom Node Pack

The user wants to install a ComfyUI custom node pack from the registry or a GitHub repository.

Instructions

  1. Parse the argument. The argument is: $ARGUMENTS

    If no argument was provided, ask the user what node pack they want to install.

    Determine the source type:

    • GitHub URL: starts with https://github.com/ — use directly
    • Registry ID: a slug like comfyui-impact-pack — search for it
    • Descriptive name: like "Impact Pack" or "ControlNet" — search for it
  2. Find the pack. If not a direct GitHub URL:

    • Call search_custom_nodes with the argument as the query
    • Present the top results: name, description, author, star count
    • If multiple matches, ask the user to confirm which one they want
    • Call get_node_pack_details with the selected pack ID for full info including the repository URL
  3. Confirm with the user. Before installing, show:

    • Pack name and description
    • Author and repository URL
    • Number of nodes included (if available)
    • Ask for explicit confirmation to proceed
  4. Determine the custom_nodes directory. The custom nodes directory is typically at the ComfyUI base path under custom_nodes/. Check get_system_stats if needed to find the ComfyUI installation path. Verify the directory exists.

  5. Clone the repository. Use the Bash tool to:

    git clone {repo_url} {custom_nodes_dir}/{pack_name}
    

    If the directory already exists, inform the user and ask if they want to update it (git pull) instead.

  6. Install dependencies. Check for dependency files in the cloned directory:

    • If requirements.txt exists: run pip install -r requirements.txt using ComfyUI's Python venv
    • If install.py exists: run it with ComfyUI's Python interpreter
    • Use the venv Python path (e.g., .venv/Scripts/python.exe on Windows or .venv/bin/python on Linux/macOS)
  7. Restart ComfyUI. Tell the user that new nodes require a restart to be loaded. Offer to call restart_comfyui to restart automatically.

Read the full file on GitHub · 69 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 69 lines · 8 tokens per session scan A dd20b636ade5

Subscribe to this mod's changes

install is a command published in the GitHub repository sandyup/comfyui-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 801 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.