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 peteromallet/VibeComfy --skill explain-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/explain-comfy-workflow)<a href="https://agentmods.dev/skills/peteromallet/vibecomfy/explain-comfy-workflow"><img src="https://agentmods.dev/badge/skills/peteromallet/vibecomfy/explain-comfy-workflow/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/peteromallet/vibecomfy/explain-comfy-workflow"><img src="https://agentmods.dev/badge/skills/peteromallet/vibecomfy/explain-comfy-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00094 | $0.00725 |
| Opus 5.5 | $0.00038 | $0.00290 |
| Sonnet 5.5 | $0.00019 | $0.00145 |
| Haiku 4.5 | $0.00009 | $0.00072 |
Grade A, and why
explain-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 1mo 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explain Comfy Workflow
Use this for understanding, not mutation. Push toward the same VibeComfy evidence path as edit/run/debug, but stop at a clear answer unless the user asks to change or execute the graph.
Fast Path
vibecomfy inspect <workflow>
vibecomfy analyze info <workflow>
If the target is raw JSON, inspect it as import evidence and use the positional-source conversion path when a Python explanation is needed:
vibecomfy import <workflow.json>
vibecomfy validate workflows/<source-stem> --json
If the question depends on class behavior, sockets, or widgets:
vibecomfy nodes spec <ClassType>
Use search-comfy-workflows only when local evidence is not enough to explain a custom node, model family, or community workflow pattern.
What To Answer
Shape the explanation around the user's question:
- what the workflow makes
- the main data path: loaders -> conditioning -> sampler/generator -> decode/output
- important public inputs, prompts, seeds, steps, dimensions, frame/audio controls, or model choices
- custom nodes, models, and missing dependencies
- likely runtime constraints or reasons it may not run
- where the answer came from: command output, node ids, file path, metadata, or run artifact
Keep it concrete. Name exact node classes and ids when they matter. Do not invent field meanings; inspect the graph or node spec.
Boundaries
- Do not edit the workflow; hand off to
edit-comfy-workflow. - Do not run GPU work just to explain a static graph; hand off to
run-comfy-workflowonly when the user asks for execution or output proof. - Do not diagnose a failure beyond the available evidence; hand off to
debug-comfy-workflowwhen logs, validation errors, or missing assets are central. - Do not search Hivemind for every question. Start with the local graph and escalate only when semantics or precedent are missing.
Return Shape
Answer in plain language with a compact evidence trail:
- target workflow or file
- short purpose summary
- main node/data path
- relevant knobs or dependencies
- uncertainties or next proof step, if any
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.
- 1mo ago Changed · +9 lines 2576ce0ea7e3
- 1mo ago Changed dc9c97bcc87d
- 1mo ago First seen · 62 lines · 94 tokens per session scan A 064c78ecfe09
explain-comfy-workflow is a skill published in the GitHub repository peteromallet/VibeComfy (152 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 725 once invoked, about $0.0004 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.