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/laurigates/claude-plugins/comfy-clinpx skills add laurigates/claude-plugins --skill comfy-cligit clone --depth 1 https://github.com/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/comfy-cli)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/comfy-cli"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/comfy-cli.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.00058 | $0.04660 |
| Opus 5 | $0.00029 | $0.02330 |
| Sonnet 5 | $0.00012 | $0.00932 |
| Haiku 4.5 | $0.00006 | $0.00466 |
Grade D, and why
comfy-cli scanned grade D with 3 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 today.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| `comfy launch [--background]` | Spawns a second ComfyUI process competing for port 8188 and the GPU against the systemd unit. Use `sudo systemctl start/stop comfyui.service` instead — the project `CLAUDE.md` covers thi Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf custom_nodes/<dir-name> Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl -s 'https://api.comfy.org/nodes/<id>/versions' | jq '.[] | {version,status}'`. How it starts
The opening of the file, as written. The whole thing — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
comfy CLI on this install
comfy (comfy-cli) is the upstream Comfy Org Python CLI. Installed here via
uv tool at ~/.local/share/uv/tools/comfy-cli/ (binary symlink at
~/.local/bin/comfy). The default workspace is already pinned to
your ComfyUI install's root — never pass --workspace, never run set-default once it's pinned.
The service runs via systemd on 0.0.0.0:8188 (see project CLAUDE.md). The
CLI's lifecycle commands assume it owns the process. Most don't apply here.
The useful surface is custom-node management, headless API execution,
and snapshots. Almost everything else is either a no-op or actively
conflicts with the systemd unit.
When to Use This Skill
| Use this skill when... | Use instead when... |
|---|---|
The user asks to use the comfy CLI - install/update/bisect nodes, snapshot/restore, publish, run workflows headlessly |
Managing custom nodes via the ComfyUI-Manager UI directly |
Running a workflow via comfy run --workflow ... --port ... |
Running headlessly over the raw HTTP API -> comfyui-pack-live-smoke |
What to use
| Task | Command |
|---|---|
| List installed custom nodes | comfy node simple-show installed |
| Install a custom node by registry name | comfy node install <name> |
| Install a node directly from the comfy registry by ID (use when Manager's curated list lags or the node was just published) | comfy node registry-install <node-id> |
| Install all custom nodes referenced by an imported workflow | comfy node install-deps --workflow path/to/workflow.json |
| Update one or more nodes | comfy node update <name> [<name> ...] |
| Update every custom node + Comfy core | comfy node update all |
Reinstall a node's requirements.txt (after a venv rebuild or import error) |
comfy node fix <name> |
| Snapshot current node state to JSON | comfy node save-snapshot --output snapshots/$(date -I).json |
| Restore a snapshot | comfy node restore-snapshot snapshots/<file>.json |
| Bisect which custom node is breaking startup | comfy node bisect start then good/bad |
| Generate a dep manifest for a workflow you're sharing | comfy node deps-in-workflow --workflow X.json --output X.deps.json |
| Run an API-format workflow against the running server | comfy run --workflow path.json --port 8188 --timeout 600 --verbose |
| Show installed models in a table | comfy model list |
| Inspect workspace / running-server state | comfy which, comfy env |
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.
- today First seen · 333 lines · 58 tokens per session scan D fced8b85cbc3
comfy-cli is a skill published in the GitHub repository laurigates/claude-plugins (57 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 4,660 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
feature-branch-pr-writing
Use this skill when the user asks to write, draft, create, or improve a PR description for a Shopware core repository PR — AND that PR targets a non-trunk feature branch (not trunk itself). Trigger phrases like "write a PR description", "draft the PR", "what should I put in the PR body". The skill detects the target…
ci-log-interpretation
Use this skill when reading or analyzing CI logs from a Shopware GitHub Actions workflow to figure out why a build failed — phrases like "why did CI fail", "what broke the build", "check the pipeline", "interpret these logs", "debug this red build" — or whenever raw run logs, job logs, or check annotations from a…
a0-create-plugin
Create, extend, or modify Agent Zero plugins. Follows strict full-stack conventions (usr/plugins, plugin.yaml, Store Gating, AgentContext, plugin settings). Use for UI hooks, API handlers, lifecycle extensions, or plugin settings UI.
a0-contribute-plugin
Guide for publishing an Agent Zero plugin to the community Plugin Index (a0-plugins repo). Covers GitHub repo setup, index.yaml creation, CI validation rules, and PR submission. Use when the user wants to share, publish, submit, or contribute a plugin to the Plugin Hub so other Agent Zero users can find and install it.
repo-activity
Scan all git repositories under /repos and report recent activity — last commit age, branch, uncommitted changes — in age-bucketed tables. Use when the user asks for a repo activity overview, "what have I been working on", portfolio status, or which repos are active/dormant.
a0-plugin-router
Main entry point for all Agent Zero plugin tasks. Routes to specialist skills for creating, reviewing, contributing, managing, or debugging plugins. Use when the user mentions plugins, asks how the plugin system works, wants to build/install/uninstall/publish/debug a plugin, or asks about the Plugin Hub.