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/hybridindie/comfyui_mcp/progressnpx skills add hybridindie/comfyui_mcp --skill progressgit clone --depth 1 https://github.com/hybridindie/comfyui_mcpWrote 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/hybridindie/comfyui_mcp/progress)<a href="https://agentmods.dev/skills/hybridindie/comfyui_mcp/progress"><img src="https://agentmods.dev/badge/skills/hybridindie/comfyui_mcp/progress.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.1 | $0.00011 | $0.00263 |
| Opus 5 | $0.00005 | $0.00131 |
| Sonnet 5 | $0.00002 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
progress 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 5d 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
Job Progress
Show progress for a specific ComfyUI job. Prompt ID: "$ARGUMENTS".
-
Get the prompt_id. Extract it from "$ARGUMENTS". If "$ARGUMENTS" is empty or contains no recognizable id, suggest the user run
/comfy:statusfirst to find active job IDs, or/comfy:historyfor recent completions, and stop here. -
Fetch progress. Call
comfyui_get_progresswith the prompt_id. Do not pre-validate the id format — the tool returnsstatus="unknown"if the job is not found, which step 3 surfaces to the user. -
Format the response. The response is a dict. Format it to include the following fields:
- Current node: which node is executing (
current_nodefield) - Progress:
stepX oftotal_stepsY (percentage) - Status: one of
queued,running,completed,error,interrupted(mapped from the unified/api/jobs/{id}endpoint), orunknownif the job is not found
- Current node: which node is executing (
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.
- 5d ago First seen · 18 lines · 11 tokens per session scan A 5aa8c61014a1
progress is a skill published in the GitHub repository hybridindie/comfyui_mcp (2 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 263 once invoked, about $0.0001 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-31.
Other skills, from other repositories
local-gpu-imagegen
Use when a user asks to create, generate, draw, render, transform, restyle, or revise a visual asset on the local GPU.
Product Photoshoot Workflow
Multi-angle product imagery workflow. Use when the user wants to "shoot a product", "make e-commerce product images", "product photography set", "电商产品图", "产品多角度图", "brand product visuals", or provides a single product photo and asks for marketing-ready variations. Produces 4 distinct directions (lifestyle scene, macro…
b123d-modeling
Use this skill when asked to model, build, or modify a 3D part or assembly with build123d — from a text description, a technical drawing (image or PDF), dimensions in a spec, or an existing STEP/STL file.
b123d-edit
Use this skill when the task is to change an existing build123d model or script: "make this bracket 5 mm taller", "move the holes inward", "add a counterbore", "remove this rib", "make it fit this mating part", or "repair the code so the intended edit remains parametric".
image-context-runtime
Use for image-heavy Codex work when generated or inspected media should stay behind a bounded MCP boundary and the controlling task should receive only durable Job IDs, hashes, relative references, and compact text handoffs.
hmem-release
Pre-publish checklist for hmem: skills synced, version bumped, tests green, nothing forgotten. Use before npm publish or when the user says 'release', 'publish', 'push a release', or 'neue Version'.