Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/espennilsen/pinpx agentmods add skills/espennilsen/pi/comfyui-node-updateWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/espennilsen/pi/comfyui-node-update)<a href="https://agentmods.dev/skills/espennilsen/pi/comfyui-node-update"><img src="https://agentmods.dev/badge/skills/espennilsen/pi/comfyui-node-update/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/espennilsen/pi/comfyui-node-update"><img src="https://agentmods.dev/badge/skills/espennilsen/pi/comfyui-node-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00119 | $0.03065 |
| Opus 5.5 | $0.00048 | $0.01226 |
| Sonnet 5.5 | $0.00024 | $0.00613 |
| Haiku 4.5 | $0.00012 | $0.00307 |
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 1mo 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.
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 |
— |
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.
- 1mo ago First seen · 357 lines · 119 tokens per session scan A decc91640a65
comfyui-node-update is a skill published in the GitHub repository espennilsen/pi (122 stars, last pushed 9d ago), licensed MIT. It adds 119 tokens to every session and 3,065 once invoked, about $0.0005 per session on Opus 5.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.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…