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.
npx agentmods add commands/artokun/comfyui-mcp/node-skillgit clone --depth 1 https://github.com/artokun/comfyui-mcpWhat 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.00012 | $0.00431 |
| Opus 5 | $0.00006 | $0.00216 |
| Sonnet 5 | $0.00002 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
node-skill 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.
What it actually says
/comfy-skill — Generate a Node Pack Skill
The user wants to generate a Claude Code skill file for a ComfyUI custom node pack.
Instructions
-
Parse the argument. The argument is: $ARGUMENTS
- A ComfyUI Registry ID (e.g.,
comfyui-impact-pack) - A GitHub repository URL (e.g.,
https://github.com/ltdrdata/ComfyUI-Impact-Pack) - Nothing, in which case ask the user which node pack they want to generate a skill for
- A ComfyUI Registry ID (e.g.,
-
Generate the skill. Use the
list_packstool with:action:"generate_skill"source: the registry ID or GitHub URLinstall_in: save toskills/<pack-name>/inside the plugin directory
-
Report the result. Tell the user:
- Where the skill file was saved
- A brief summary of what nodes are covered
- That they may need to restart Claude Code for the skill to take effect
Example
User: /comfy-skill comfyui-impact-pack
Steps:
- Call
list_packswithaction: "generate_skill", source"comfyui-impact-pack"andinstall_inset to the skills directory - Show the user where the file was saved and what it covers
Notes
- The generated skill includes node class types, input/output specs, usage examples, and a
## Sourcessection (official repo README vs empirically-tuned composition patterns) - Skills are saved as
SKILL.mdfiles in subdirectories under the plugin'sskills/folder - If the node pack isn't found in the registry, suggest the user provide a GitHub URL instead
- If nodes from the pack are installed locally, the skill will include live
/object_infodata
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 · 41 lines · 12 tokens per session scan A 7354cb31eb34
node-skill is a command published in the GitHub repository artokun/comfyui-mcp (701 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 431 once invoked, about $0.0001 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.
Other commands, from other repositories
setup
You are setting up the Video Recreation Agent Team inside this comfyui-agent repo. Run every step below automatically. Don't ask permission — just do it, report what happened.
PRODUCTION_HARDEN
Each agent is a Claude Code sub-agent invoked via claude --model claude-sonnet-4-6-20250929 with a role-specific prompt file. Agents operate on branches, submit PRs via conventional commits.
PRODUCER
You are the production manager for this open-source VFX tool. You handle everything that's NOT the code itself: CI/CD, packaging, release management, documentation infrastructure, metrics, and cross-agent coordination. You're the one who makes sure the train runs on time and nothing ships broken.
qa-compare
You are the QA expert in the Video Recreation Agent Team.
COMFY_LEAD
You are the ComfyUI technical lead. You know ComfyUI's API, node system, workflow JSON format, and the MCP protocol deeply. You're hardening an AI co-pilot that helps VFX artists work with ComfyUI through natural language.
NUKE_COMP
You are a senior VFX compositor with deep Nuke pipeline experience who has transitioned into pipeline TD work. You think about tool integration the way a compositor thinks about a comp tree — everything must connect cleanly, data must flow predictably, and the artist should never have to think about the plumbing.