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/peteromallet/vibecomfy/debug-comfy-workflownpx skills add peteromallet/VibeComfy --skill debug-comfy-workflowgit clone --depth 1 https://github.com/peteromallet/VibeComfyWrote 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/peteromallet/vibecomfy/debug-comfy-workflow)<a href="https://agentmods.dev/skills/peteromallet/vibecomfy/debug-comfy-workflow"><img src="https://agentmods.dev/badge/skills/peteromallet/vibecomfy/debug-comfy-workflow.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00070 | $0.00406 |
| Opus 5 | $0.00035 | $0.00203 |
| Sonnet 5 | $0.00014 | $0.00081 |
| Haiku 4.5 | $0.00007 | $0.00041 |
Grade A, and why
debug-comfy-workflow 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 4d 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
Debug Comfy Workflow
Debug from cheap static evidence toward expensive runtime evidence. Decide first whether the failure is the graph, dependencies, or the runtime.
First Pass
vibecomfy inspect <workflow>
vibecomfy validate <workflow>
vibecomfy doctor <workflow> --json
vibecomfy analyze info <workflow>
For source JSON or conversion failures:
vibecomfy port check <workflow.json> --json
vibecomfy port doctor-all <workflow.json> --json
vibecomfy port widgets <workflow.json> --json
For runtime failures:
vibecomfy runtime doctor
vibecomfy logs tail
vibecomfy watchdog list
Missing Nodes Or Models
vibecomfy nodes install-plan <workflow>
vibecomfy nodes spec <ClassType>
vibecomfy fetch <workflow> --dry-run
vibecomfy models stage --select-phase core --dry-run
Install or download only after the evidence supports it and the user agrees.
Discipline
- Keep graph errors separate from environment errors.
- If embedded ComfyUI is not discoverable, use
vibecomfy-setup; that is not a workflow bug. - Do not recommend arbitrary node packs. Require
nodes install-plan, lockfile data, registry evidence, or a concrete precedent. - If class/schema evidence is missing, use
search-comfy-workflowsbefore patching. - Preserve report paths and cite the exact command output or file that supports the diagnosis.
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.
- 4d ago First seen · 53 lines · 70 tokens per session scan A 0ac5bd4026bb
debug-comfy-workflow is a skill published in the GitHub repository peteromallet/VibeComfy (146 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 406 once invoked, about $0.0003 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
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…