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 agent-skillgit 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/agent-skill)<a href="https://agentmods.dev/skills/peteromallet/vibecomfy/agent-skill"><img src="https://agentmods.dev/badge/skills/peteromallet/vibecomfy/agent-skill/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/agent-skill"><img src="https://agentmods.dev/badge/skills/peteromallet/vibecomfy/agent-skill.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.00099 | $0.03232 |
| Opus 5.5 | $0.00040 | $0.01293 |
| Sonnet 5.5 | $0.00020 | $0.00646 |
| Haiku 4.5 | $0.00010 | $0.00323 |
Grade A, and why
vibecomfy 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VibeComfy
VibeComfy is this package: a Python-first way to drive ComfyUI without hand-editing JSON. The center of gravity is VibeWorkflow: load a workflow, edit it in Python, validate it, then compile to ComfyUI API JSON and run it.
Use this umbrella skill for orientation and package rules. For real work, route to the smallest focused skill:
| User wants | Use |
|---|---|
| Configure ComfyUI paths, server URL, custom nodes, or models | vibecomfy-setup |
| Find a workflow, precedent, node wiring, or Hivemind evidence | search-comfy-workflows |
| Explain what a workflow does or answer questions about it | explain-comfy-workflow |
| Clean up, regroup, or align a ComfyUI workflow layout without changing runtime behavior | reorganise-comfy-workflow |
| Tweak or rewrite a workflow without running it | edit-comfy-workflow |
| Execute a ready template, recipe, scratchpad, server run, or RunPod smoke | run-comfy-workflow |
| Diagnose validation, conversion, node/model, or runtime failures | debug-comfy-workflow |
| Add a durable package ready template | add-comfy-workflow-template |
The operating path is:
discover -> load_bundle -> edit/compose -> validate -> compile("api") -> run -> collect outputs
Custom Python functions use @python_node and lower to visible, executable
vibecomfy.exec nodes. Complete modules/projects use
python_node.from_source with a bounded source capsule; worker-installed
packages use python_node.from_installed. Route authoring and source edits
to edit-comfy-workflow, execution and queue evidence to
run-comfy-workflow, and dependency/import failures to
vibecomfy-setup or debug-comfy-workflow. Read
custom Python workflow nodes for the
canonical syntax and validation boundaries.
For a reusable source-to-Python onboarding path, including provenance and honest import/runtime blockers, see workflow onboarding.
First Moves
Work from the user's project directory so relative import destinations and
recipe paths are predictable. Repository maintenance commands may require the
VibeComfy repo root. Prefer the vibecomfy ... console entrypoint; if an
editable checkout has no console script, use python -m vibecomfy.cli ....
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- README.md 2.8 KB
- REFERENCE.md 18 KB
- skills/add-comfy-workflow-template/SKILL.md 2.7 KB
- skills/debug-comfy-workflow/SKILL.md 2.4 KB
- skills/edit-comfy-workflow/SKILL.md 8.5 KB
- skills/explain-comfy-workflow/SKILL.md 3.1 KB
- skills/reorganise-comfy-workflow/SKILL.md 5.5 KB
- skills/run-comfy-workflow/SKILL.md 6.8 KB
- skills/search-comfy-workflows/SKILL.md 3.8 KB
- skills/vibecomfy-setup/SKILL.md 6.0 KB
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 · +15 lines e1307e089039
- 1mo ago Changed · +27 lines 2554e88f14bc
- 1mo ago Changed · +17 lines 7506ed8e6f4e
- 1mo ago Changed · +27 lines dcb374d0730b
- 1mo ago Changed · +4 lines 0b5605833918
- 1mo ago First seen · 148 lines · 99 tokens per session scan A 83a4ee6ea757
vibecomfy is a skill published in the GitHub repository peteromallet/VibeComfy (152 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 3,232 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.