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 skills add artokun/comfyui-mcp --skill troubleshootinggit clone --depth 1 https://github.com/artokun/comfyui-mcpWrote 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/artokun/comfyui-mcp/troubleshooting)<a href="https://agentmods.dev/skills/artokun/comfyui-mcp/troubleshooting"><img src="https://agentmods.dev/badge/skills/artokun/comfyui-mcp/troubleshooting/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/artokun/comfyui-mcp/troubleshooting"><img src="https://agentmods.dev/badge/skills/artokun/comfyui-mcp/troubleshooting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 264 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00028 | $0.04886 |
| Opus 5 | $0.00014 | $0.02443 |
| Sonnet 5 | $0.00006 | $0.00977 |
| Haiku 4.5 | $0.00003 | $0.00489 |
Grade A, and why
troubleshooting 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 10d 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 — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ComfyUI Troubleshooting Guide
Render completes but looks WRONG (artifacts, wrong subject/pose/color, a ControlNet/mask/LoRA not taking, a refiner degrading it)? That's not an error. Use the debug-render skill (
list_packswithaction: "skill_read",name: "debug-render") to localize the bad stage with run-to-node (panel_runto_node_id) by previewing intermediate steps. This guide is for runs that fail with an error, OOM, or missing node.
Error Diagnosis Strategy
When a workflow fails, follow this approach:
- Get the error. Use
get_history(action="diagnose")to retrieve the execution result with the full traceback, plus any missing models/nodes - Check logs. Use
get_system_stats (action:"logs")with keyword filters like"error","warning","traceback" - Identify the failing node. The history response includes the
node_idandnode_typethat failed - Cross-reference inputs. Use
create_workflow (action:"node_info")to verify the failing node's expected input schema - Check models. Use
list_local_modelsto verify all referenced model files exist
Out of Memory (OOM)
Error Pattern
torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate X MiB.
GPU 0 has a total capacity of 24.00 GiB of which X MiB is free.
Or:
RuntimeError: CUDA error: out of memory
Root Cause
The GPU does not have enough VRAM to hold the model weights, intermediate tensors, and latent images at the same time. Common triggers:
- High resolution images (2048x2048+)
- Multiple models loaded at the same time
- FP32 precision models on limited VRAM
- Video generation (LTXV, AnimateDiff) with many frames
- Large batch sizes
Fixes (in order of preference)
- Reduce resolution. Drop to the model's native resolution (512 for SD 1.5, 1024 for SDXL/Flux)
- Use FP8/FP16 quantized models. FP8 Flux models use ~8GB vs ~24GB for FP16
- Search for FP8 variants:
download_model({ action: "search", query: "flux fp8" })or the same with"sdxl fp8"
- Search for FP8 variants:
- Launch flags (the VRAM ladder). Offload via ComfyUI CLI flags:
--lowvramoffloads text encoders / model parts to CPU--novramis extreme offload, the go-to for long video (LTX 2 / WAN) OOM--cache-nonecaches nothing (lowest RAM/VRAM); combine with--novram--reserve-vram Nreserves N GB so the GPU stops spilling into slow shared VRAM (Windows); typical2to4--disable-smart-memoryforces offload to RAM when a run gets stuck or OOMs intermittently- Full matrix and recipes:
comfyui-launch-flags
- Free VRAM between generations. ComfyUI should auto-manage, but restarting clears leaked memory
- Use tiled VAE decoding. For high-resolution images, tile the VAE decode step
- Node:
VAEDecodeTiledinstead ofVAEDecode - Breaks the image into tiles, decodes each separately, and stitches them together
- Node:
- Reduce batch size. Set batch_size to 1 in
EmptyLatentImage - Avoid multiple models. Don't load two full checkpoints at the same time; use one checkpoint and LoRAs instead
- For LTXV/video: always use FP8 quantized video models on 24GB cards
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.
- 10d ago First seen · 500 lines · 28 tokens per session scan A eea426b5af1b
troubleshooting is a skill published in the GitHub repository artokun/comfyui-mcp (735 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 4,886 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 skills, from other repositories
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…
ci-debug
Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…
paired-probe
Refuse a verdict a probe did not earn. Runs a check where the fault IS present and where it is NOT, and blocks the answer when both arms print the same thing, because a check that cannot disagree with you has measured nothing. Also catches the zero-sample sweep that reads as "clean" and the swallowed error that reads…
analyze
Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z", "trace the auth path", "explore the codebase…
audit-installation
An audit tool for checking whether an IWE installation is complete, healthy, and consistent with its templates. It reports results for files, customizations, connections, and a basic workflow test.
debug
Systematically diagnose and resolve bugs through conversational investigation and root cause analysis.