Wildcard List Inspector 📋

Wildcard files are the easiest part of a prompt library to lose track of. You accumulate a dozen .txt files - colors, outfits, lighting moods - and pretty soon you can't remember what's called what, let alone what's inside. Wildcard List Inspector is the inventory. It scans the same wildcards folder the pack's Wildcard Loader reads, and lists every file with its line count and a preview of the first few entries.

It's a browse-the-drawer node, and it's genuinely useful for one specific thing: turning "I know I had a file for this somewhere" into a remembered name in about five seconds.

How it works

It resolves the wildcards folder the same way the pack's Wildcard Loader does, with a priority order:

1. <ComfyUI root>/wildcards/ - the shared convention used by Impact Pack, Dynamic Prompts, and A1111-style extensions, so existing wildcard collections get picked up automatically.
2. The pack's bundled wildcards/ folder - a fallback that the loader auto-creates with two starter files (color.txt, quality.txt) so the feature works with zero setup.

For every .txt file it finds it reports the wildcard name - the thing that goes between double underscores - the count of usable lines (blank lines and # comments don't count), and a preview of the first preview_lines. The preview makes it way faster to find the right file than opening a file browser, because you see the actual content, not just a filename.

Inputs and outputs

One input, honestly: preview_lines (default 3, up to 20) controls how many lines of each file's preview you get. Crank it to 20 when you're deciding between two similar files; leave it at 3 for the everyday inventory view.

Outputs are listing (the whole report as a STRING - wire it into a text display or log node) and file_count (an INT, useful for a "how many do I have" sanity check or automation).

Install

cd ComfyUI/custom_nodes
git clone https://github.com/TensorVizion/OmniNodes

Restart ComfyUI; find Wildcard List Inspector 📋 under TensorVizion/Prompt. No extra dependencies - it's pure Python and ComfyUI's folder_paths.

Where people get burned

• It only sees the folders the pack resolves. If your wildcards live somewhere exotic - another extension's custom location, a subfolder you invented - this won't list them. It scans wildcards/ at the ComfyUI root and the pack's own bundled folder, period.
• Empty folder gives a helpful hint, not an error. If nothing exists yet, the listing output literally tells you to run Wildcard Loader once, which creates the folder and seeds the starter files. So the workflow is: run the loader once, then inspect.
• Subfolders work, and the name includes the path. Files in nested folders are reported as folder/name, which is exactly how you'd reference them in __folder/name__ syntax. Good to know before you write a token that doesn't match.

The one-liner: it's not a node that does heavy lifting, but it's the difference between remembering you had a wildcard file and knowing its exact name. Once you've got the name, the real tool - Wildcard Loader - takes over.