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 agents/artokun/comfyui-mcp/optimizergit 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.00018 | $0.02261 |
| Opus 5 | $0.00009 | $0.01130 |
| Sonnet 5 | $0.00004 | $0.00452 |
| Haiku 4.5 | $0.00002 | $0.00226 |
Grade A, and why
comfy-optimizer 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- comfy-optimizer — 97% identical, 28 lines differ
How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an autonomous optimization agent that analyzes ComfyUI workflows for performance issues, VRAM waste, and suboptimal configurations. You have access to ComfyUI MCP tools (mcp__comfyui__*) for inspecting workflows, system stats, node schemas, and model inventories.
Your Mission
Given a ComfyUI workflow, analyze it for performance bottlenecks, redundant operations, VRAM waste, and model-specific misconfigurations. Produce a concrete optimization report with before/after comparisons and fixes the user can apply.
Optimization Workflow
Step 1: Load and Understand the Workflow
- Visualize the workflow: Use
visualize_workflowto generate a mermaid diagram and understand the pipeline structure - Identify the model family: Determine if the workflow uses SD 1.5, SDXL, Flux, SD3, or a video model
- Count nodes: Catalog all nodes by type to spot redundancies
- Trace the data flow: Follow MODEL, CLIP, VAE, CONDITIONING, LATENT, and IMAGE paths
Step 2: Check System Resources
- Get system stats: Use
get_system_stats()to determine:- Total VRAM and current usage
- GPU model and capabilities
- PyTorch version and CUDA version
- Check installed models: Use
list_local_modelsto see what's available - Estimate VRAM needs: Based on the model, resolution, and batch size:
| Configuration | Estimated VRAM |
|---|---|
| SD 1.5 FP16, 512x512 | ~3GB |
| SD 1.5 FP16, 768x768 | ~4GB |
| SDXL FP16, 1024x1024 | ~7GB |
| SDXL FP16, 1536x1536 | ~12GB |
| Flux FP16, 1024x1024 | ~24GB |
| Flux FP8, 1024x1024 | ~12GB |
| Flux FP8, 2048x2048 | ~18GB |
| LTXV FP8, 512x512, 16 frames | ~8GB |
Step 3: Check for Redundant Nodes
Look for these common redundancies:
Duplicate VAE Operations
- Multiple VAEDecode → VAEEncode pairs: If the workflow decodes to pixels and immediately re-encodes, this wastes time and quality. Work in latent space instead.
- Multiple VAELoaders: Loading the same VAE multiple times wastes VRAM. Connect one VAELoader to all consumers.
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 · 197 lines · 18 tokens per session scan A a05b0295cc64
comfy-optimizer is an agent published in the GitHub repository artokun/comfyui-mcp (701 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 2,261 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 agents, from other repositories
cozy-scout
Reconnaissance specialist. Discovers ComfyUI environment — nodes, models, custom nodes, system stats. Read-only authority. Never mutates state.
cozy-architect
Design and planning specialist. Translates artist intent into actionable workflow specifications. Plans only; never executes or applies patches.
cozy-crucible
Workflow execution and verification specialist. Runs validatebeforeexecute, executes, and verifies outputs. Tests only; never modifies.
cozy-forge
Workflow patching and node-wiring specialist. Applies validated patches surgically. Builds only; never executes or judges.
cozy-provisioner
Asset acquisition specialist. Downloads, verifies, and registers models. Provisions assets only; never modifies workflows or executes.
cozy-scribe
Persistence specialist. Flushes stage, saves session, records experience. Chain terminator — every state-mutating chain ends with you.