What is comfyui-node-update?

A documentation writer for ComfyUI nodes, which are visual workflow building blocks. It creates beginner-friendly descriptions, tips, and other content in separate JSON files for each node.

Use it to document new or updated nodes, fill empty descriptions, improve existing text, add usage tips, or write documentation in batches.

It makes node documentation easier to understand while keeping the data organized by node type and category.

comfyui-node-update — Skill by espennilsen

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 skills/espennilsen/pi/comfyui-node-update

Any agent

npx skills add espennilsen/pi --skill comfyui-node-update

Clone the repo

git clone --depth 1 https://github.com/espennilsen/pi

Made for: Claude Code, Codex.

Per session 119 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,065 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.

Model	Per session	Once invoked
Fable 5	$0.00119	$0.03065
Opus 5	$0.00060	$0.01533
Sonnet 5	$0.00024	$0.00613
Haiku 4.5	$0.00012	$0.00307

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

Security

Grade A, and why

comfyui-node-update 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 3d ago.

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.

skills/comfyui-node-update/SKILL.md · 357 lines

How it starts

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

Node Documentation Writer

Write original, beginner-friendly documentation for ComfyUI nodes. Each node is stored as an individual JSON file. Use the embedded docs as a reference source but always rewrite content — never copy-paste.

File Structure

Node data is split into per-node JSON files organized by section and category:

src/data/nodes/
  _metadata.json                              — metadata + schema_version
  comfy_nodes/<category>/<NodeName>.json      — core ComfyUI nodes (511)
  partner_nodes/<category>/<NodeName>.json    — API/partner nodes (203)
  subgraph_blueprints/<category>/<Name>.json  — subgraph blueprints (65)
  extensions/<category>/<NodeName>.json       — extension nodes (1)

The top-level directories (comfy_nodes, partner_nodes, subgraph_blueprints, extensions) match the tree pane sections. Below that, the category path matches the node's category field with spaces replaced by hyphens.

Key files

Per-node data: src/data/nodes/<section>/<category>/<NodeName>.json
Metadata: src/data/nodes/_metadata.json
Export data: exports/comfyui_nodes_*.json (structural source of truth)
Embedded docs: embedded-docs/comfyui_embedded_docs/docs/<NodeName>/en.md (reference only)
Update plan: exports/NODE_UPDATE_PLAN.md (progress tracking)
Extraction script: scripts/extract-comfyui-nodes.sh (pulls from running ComfyUI)
Import script: scripts/import-new-nodes.sh (creates skeletal files, updates metadata)

Finding a node file

To locate a node's JSON file:

find src/data/nodes -name 'KSampler.json'
# → src/data/nodes/comfy_nodes/sampling/KSampler.json

To search across all nodes:

rg '"documentation_complete": false' src/data/nodes/ -l

Content Fields to Write

For each node, write these fields:

Field	What to write	Length
`description`	Technical but clear explanation of what the node does	50–200 chars
`beginner_description`	Plain-language explanation for someone new to ComfyUI	100–400 chars
`tips.general_tips`	Practical advice any user should know	2–5 tips
`tips.beginner_tips`	"Start here" guidance with specific values and settings	2–4 tips
`tips.advanced_tips`	Power-user techniques, edge cases, combo strategies	1–4 tips (skip for simple nodes)
`use_cases`	Concrete scenarios with context	2–4 use cases
`common_errors`	Real problems users hit, with actionable fixes	1–4 errors
`complexity_level`	`"beginner"`, `"intermediate"`, or `"advanced"`	—
`documentation_complete`	Set `true` when all content fields are filled	—

Read the full file on GitHub · 357 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.

3d ago First seen · 357 lines · 119 tokens per session scan A decc91640a65

Subscribe to this mod's changes

comfyui-node-update is a skill published in the GitHub repository espennilsen/pi (117 stars, last pushed 10d ago), licensed MIT. It adds 119 tokens to every session and 3,065 once invoked, about $0.0006 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-30.

Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens