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 edit-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/edit-comfy-workflow)<a href="https://agentmods.dev/skills/peteromallet/vibecomfy/edit-comfy-workflow"><img src="https://agentmods.dev/badge/skills/peteromallet/vibecomfy/edit-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/edit-comfy-workflow"><img src="https://agentmods.dev/badge/skills/peteromallet/vibecomfy/edit-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.00072 | $0.02019 |
| Opus 5.5 | $0.00029 | $0.00808 |
| Sonnet 5.5 | $0.00014 | $0.00404 |
| Haiku 4.5 | $0.00007 | $0.00202 |
Grade A, and why
edit-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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Edit Comfy Workflow
Use this when the graph needs to change. Follow the same shape as the agentic tests: identify the target, inspect it, materialize an editable Python surface if needed, make the smallest graph change, then validate.
Shared Edit Spine
Use the same spine as the Comfy app agent edit path and the structural/live agentic tests:
target graph -> inspect/research -> Python editable surface -> VibeWorkflow edit -> finalize_metadata -> validate/doctor -> candidate or run
For package-side edits, the editable surface is a recipe, scratchpad, or ready template. For the Comfy app, the same idea returns a candidate UI graph plus apply eligibility. Do not treat an edit candidate as an executed result; execution belongs to run-comfy-workflow.
Fast Path
vibecomfy inspect <target>
vibecomfy analyze info <target>
If the target is raw JSON, load it only as import evidence and materialize Python before editing:
vibecomfy import <workflow.json>
vibecomfy inspect workflows/<source-stem> --json
vibecomfy edit workflows/<source-stem> targets
vibecomfy edit workflows/<source-stem> set sampler.steps 30
vibecomfy validate workflows/<source-stem> --json
The import folder contains editable workflow.py, its canonical
workflow.vibe.json companion, and byte-identical source.json; provenance
stays in the bundle metadata. Standalone import and edit are local and
untracked by default. To record origin and accepted changes in Astrid, add
--project <existing-project> to the standalone import and edit commands.
For edits, put common options after the bundle and before the verb, for example
vibecomfy edit workflows/my_workflow --project demo set sampler.steps 30.
If you are already using Astrid, use its native media import followed by a
vibecomfy.import task; Astrid supplies the project/task context, so the
executor does not take VibeComfy's --project option. The
workflow onboarding guide gives the
Astrid-native task command and history path.
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 · +40 lines a3ec29a074c8
- 1mo ago Changed · +60 lines 89f72986729c
- 1mo ago Changed 1512b66ec546
- 1mo ago First seen · 97 lines · 72 tokens per session scan A f3885679f94c
edit-comfy-workflow is a skill published in the GitHub repository peteromallet/VibeComfy (152 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 2,019 once invoked, about $0.0003 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.