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 skills/sandyup/comfyui-mcp/workflow-layoutnpx skills add sandyup/comfyui-mcp --skill workflow-layoutgit clone --depth 1 https://github.com/sandyup/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.00079 | $0.02306 |
| Opus 5 | $0.00039 | $0.01153 |
| Sonnet 5 | $0.00016 | $0.00461 |
| Haiku 4.5 | $0.00008 | $0.00231 |
Grade A, and why
workflow-layout 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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ComfyUI Workflow Layout & Organization
Turn a tangled graph into a clean left-to-right dataflow a human reads at a glance,
using the panel_* canvas tools. The golden rule: never lay out blind — read the
real node sizes and rail positions first, then compute positions from them.
Primitives (panel tools)
panel_get_graph— READ FIRST, every time. Returns, for the graph you're viewing:- each node's
pos[x,y],size[w,h] (body only), andfull_height(the TRUE rendered footprint = title bar + body; use this for vertical stacking), - all
groups(id,title,color,bounding [x,y,w,h]), - and — only when inside a subgraph — the
rails: theinput/outputboundary node positions. Everything below is computed from these numbers.
- each node's
panel_move_node(node_id, [x,y]),panel_set_node_title(node_id, title),panel_set_node_collapsed(node_id, collapsed)(minimize to title bar),panel_set_node_color(node_id, {preset|color|bgcolor})(color-code stages — presets: red/brown/green/blue/pale_blue/cyan/purple/yellow/black)- Groups (colored boxes; nodes stay put):
panel_create_group(passnode_idsto auto-wrap, orbounds [x,y,w,h];colorhex),panel_move_group,panel_edit_group,panel_remove_group. - Subgraphs (nest nodes into one collapsible node):
panel_create_subgraph(node_ids),panel_enter_subgraph/panel_exit_subgraph,panel_get_subgraph,panel_promote_widget,panel_move_rail(rail, [x,y])(rail="input"|"output", must be inside the subgraph),panel_expose_subgraph_output(from_node_id, from_output)/panel_expose_subgraph_input(to_node_id, to_input)(expose an interior slot on the boundary rail — must be inside the subgraph), andpanel_unpack_subgraph(node_id)(expand/dissolve a subgraph back into the parent — the inverse ofpanel_create_subgraph). panel_canvas({action:"fit"})to frame the result;panel_save_workflowto persist.
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.
- yesterday First seen · 137 lines · 79 tokens per session scan A 87bb41dbab35
workflow-layout is a skill published in the GitHub repository sandyup/comfyui-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 2,306 once invoked, about $0.0004 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.