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 dagthomas/comfyui_dagthomas --skill h3-ref2vagit clone --depth 1 https://github.com/dagthomas/comfyui_dagthomasWrote 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/dagthomas/comfyui_dagthomas/h3-ref2va)<a href="https://agentmods.dev/skills/dagthomas/comfyui_dagthomas/h3-ref2va"><img src="https://agentmods.dev/badge/skills/dagthomas/comfyui_dagthomas/h3-ref2va/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/dagthomas/comfyui_dagthomas/h3-ref2va"><img src="https://agentmods.dev/badge/skills/dagthomas/comfyui_dagthomas/h3-ref2va.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.00146 | $0.01152 |
| Opus 5.5 | $0.00058 | $0.00461 |
| Sonnet 5.5 | $0.00029 | $0.00230 |
| Haiku 4.5 | $0.00015 | $0.00115 |
Grade A, and why
h3-ref2va 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
H3 Ref2VA (full-reference mode)
This is what the APNext H3 Reference Prompt Writer and APNext H3 Claude Code Reference Writer nodes expect back. No alignment line. Six labels, exactly once, in this order,
each followed by one blank line - the node splits on them:
subject_definitions:
summary:
retention_analysis:
detailed_description:
overall_soundscape:
non_diegetic_music:
How the node's images map
The node has sockets image_1 ... image_9, mirrors ComfyUI's MiniMax H3 Reference to
Video node, and passes each image back out on the same-numbered output. So:
- Attached image k IS
<Picture k>. Never renumber, skip or merge pictures; the video model will receive them in that order. - Videos and audio cannot be attached to the writer node. When
reference_notesdescribe them ("Video 1 is the dance clip", "Audio 1 is her voice"), define<Video N>/<Audio N>from the notes in the order given, and treat those notes as fact. - Only the first frame of a batched input counts as that reference.
The reference_role directive
The node states how to treat the images:
- Auto - decide per image: a
<Subject N>for reusable visible content, a standalone<Picture N>for a concrete frame or composition anchor, or only a source cited inside another item's definition. - Subject - one
<Subject N>per image, citing<Picture k>inside the definition; no standalone picture entries. - Picture - one standalone
<Picture N>per image, stating which shot and position (first frame, keyframe, last frame) it anchors. - Style reference only - no standalone
<Picture N>entries; fold the style provenance into the relevant<Subject N>definitions and the style sentence before[Shot 1]. - Storyboard - standalone
<Picture N>entries stating which shots they map to and what planning information they carry.
Roles
<Subject N>= reusable visible reference content, or reusable visual / performance / style attributes. One line per subject, sourced from the pictures, videos or audio it draws on.- Standalone
<Picture N>= frame, keyframe or composition anchor only. <Video N>= editing, continuation, camera, cuts, rhythm or temporal structure.<Audio N>= copied or referenced audio.
What ships with it
3 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.
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 First seen · 90 lines · 146 tokens per session scan A 1f989fe14da6
h3-ref2va is a skill published in the GitHub repository dagthomas/comfyui_dagthomas (291 stars, last pushed 1mo ago), licensed MIT. It adds 146 tokens to every session and 1,152 once invoked, about $0.0006 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.