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 Sunwood-ai-labs/LTX23-ComfyUI-skill --skill ltx23-comfyui-skillgit clone --depth 1 https://github.com/Sunwood-ai-labs/LTX23-ComfyUI-skillWrote 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/sunwood-ai-labs/ltx23-comfyui-skill/ltx23-comfyui-skill)<a href="https://agentmods.dev/skills/sunwood-ai-labs/ltx23-comfyui-skill/ltx23-comfyui-skill"><img src="https://agentmods.dev/badge/skills/sunwood-ai-labs/ltx23-comfyui-skill/ltx23-comfyui-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/sunwood-ai-labs/ltx23-comfyui-skill/ltx23-comfyui-skill"><img src="https://agentmods.dev/badge/skills/sunwood-ai-labs/ltx23-comfyui-skill/ltx23-comfyui-skill.svg" alt="Reviewed on agentmods" width="80" 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.00074 | $0.02248 |
| Opus 5 | $0.00037 | $0.01124 |
| Sonnet 5 | $0.00015 | $0.00450 |
| Haiku 4.5 | $0.00007 | $0.00225 |
Grade A, and why
ltx23-comfyui-ti2v-audio 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 12d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LTX2.3 ComfyUI TI2V + Audio
Use this skill when the user wants to work from sources/upstream/isi-dev/LTX_2.3_Image_or_Text_&_Audio_2_Video_App_V3.json or sources/upstream/isi-dev/ComfyUI_LTX2_3_TI2V.ipynb, or when they want LTX 2.3 text/image plus audio to video in ComfyUI.
Start Here
- Preserve the upstream artifacts under
sources/upstream/isi-dev/as read-only references. - Prefer the scripted bootstrap path first.
- local setup launcher: scripts/run-remote-gpu-setup.ps1
- local start launcher: scripts/run-remote-gpu-start.ps1
- remote installer: scripts/setup-remote-ltx23-comfyui.sh
- remote starter: scripts/start-remote-comfyui.sh
- detailed usage: references/scripted-setup.md
- Read references/source-materials.md if provenance or upstream comparison matters.
- Read references/setup-and-models.md before environment or model work.
- Read references/experiment-tracking.md when running real sweeps or comparing model variants on the remote GPU machine.
- Read references/operational-lessons.md before repeating a setup or generation workflow that previously failed.
- Read references/usage-and-parameters.md before changing prompts or generation settings.
- Use sources/api/ltx23-ti2v-audio-api-prompt.json as the committed API-format base prompt when queueing runs directly through ComfyUI
/prompt. - If you add Python helpers in this repo, run them with
uv run ....
Choose the Source of Truth
- Use the App JSON when the task is "import this into ComfyUI" or "explain which controls the App exposes".
- Use the notebook when the task is "bootstrap the remote GPU machine / ComfyUI stack" or "recover the dependency list".
- Use the committed API prompt when the task is "run this workflow through ComfyUI API without repeating the UI export step".
- When the task is actual environment setup on a remote Linux GPU host, prefer running the scripted bootstrap that was derived from the notebook instead of replaying notebook shell lines manually.
- When notebook notes and graph internals disagree, prefer the actual JSON graph for exposed controls and use the notes as soft operating guidance. Call out mismatches instead of flattening them.
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.
- 12d ago First seen · 125 lines · 74 tokens per session scan A c0245506accc
ltx23-comfyui-ti2v-audio is a skill published in the GitHub repository Sunwood-ai-labs/LTX23-ComfyUI-skill (5 stars, last pushed 5mo ago), licensed MIT. It adds 74 tokens to every session and 2,248 once invoked, about $0.0004 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
lanshu-create-ai-presenter-video
Turn a topic or finished script plus an authorized adult presenter image into a complete, publish-ready AI presenter video. Use for new presenter videos and for continuing, revising, captioning, lip-sync repairing, or re-exporting an existing presenter-video job. Keep model and provider selection capability-based and…
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
open-video
Generate, edit, or direct videos via open-source models (MiniMax H3 baseline; Wan2.2 / LTX future). Use when the user wants to turn a concept, script, or reference image into a finished video or multi-shot film — single shots, image-to-video, first-last-frame interpolation, reference-video/audio styling, or stitched…
excalidraw
Create, inspect, and edit Excalidraw diagrams as editable .excalidraw JSON files. Use when Codex needs to turn architecture sketches, process flows, user journeys, system diagrams, workshop notes, whiteboard-style visuals, or Mermaid-like node-and-edge specs into an Excalidraw file; modify existing Excalidraw scenes…
seedance-2-5-prompt-director
A skill for writing and improving prompts for Seedance 2.5, a video-generation system. It covers text-to-video, image-to-video, editing, video extension, references, camera movement, green-screen work, sound, and lip sync.
h3-video
OpenVideo skill (v0.0.1): generate high-quality local video with the OpenVideo product (MiniMax H3 backend). Use for OpenVideo install/pull/status/run, official 3-field prompts, T2V/I2V/FL2VA, agent-driven video. Brand is OpenVideo — not a bare ComfyUI workflow. Triggers: OpenVideo, open-video, H3, generate video…