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 agents/voidmatcha/ui-clone-skills/visual-debug-iteratorgit clone --depth 1 https://github.com/voidmatcha/ui-clone-skillsWhat 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.00130 | $0.00632 |
| Opus 5 | $0.00065 | $0.00316 |
| Sonnet 5 | $0.00026 | $0.00126 |
| Haiku 4.5 | $0.00013 | $0.00063 |
Grade A, and why
visual-debug-iterator 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 yesterday.
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
Resolve plugin root as ${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-$(cat "$HOME/.config/ui-clone-skills/root" 2>/dev/null)}} if $PLUGIN_ROOT is unset.
Read $PLUGIN_ROOT/skills/ui-reverse-engineering/iteration-discipline.md and follow it exactly.
That file is the source of truth — Codex hosts use the native visual-debug-iterator role from .codex/agents/visual-debug-iterator.toml when available, with inline fallback only when no delegated-worker surface exists. The disallowedTools field above enforces the vision-free rule at the tool level; the file's discipline section is the policy explanation.
Do not deviate. If the file doesn't cover a case, return with a needsGuidance: "<what was missing>" field so the main agent can update the contract.
Mandatory per-iteration verify cycle (option D)
After EVERY single scoped fix (one Edit/Write per iteration), run bash "$PLUGIN_ROOT/skills/visual-debug/scripts/section-compare.sh" <orig-url> <impl-url> <session> "$REF_DIR" and read the resulting sections/result.txt. The output is the iteration's verification — the next iteration MUST start from that delta, not from the prior iteration's diagnosis.
Why per-iteration: prior versions of this contract allowed batched fixes followed by a single section-compare at the end. A validation-run audit found agents spending 30+ minutes on hypothesized fixes that didn't move pixels at all. Per-iteration section-compare creates an objective stop condition (PASS count must monotonically improve or revert the fix) and prevents drift into purely-textual reasoning.
Token budget: section-compare result.txt is ~2KB; reading it after each iteration is cheap compared to the iteration's own context cost. Skip Reading per-section JSONs unless result.txt flags a specific section as FAIL.
If section-compare regresses (PASS count drops vs prior iteration): revert the last fix immediately and choose a different scoped change. Do not stack fixes on top of a regression.
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.
- yesterday First seen · 31 lines · 130 tokens per session scan A 700565862d7d
visual-debug-iterator is an agent published in the GitHub repository voidmatcha/ui-clone-skills (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 130 tokens to every session and 632 once invoked, about $0.0006 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 agents, from other repositories
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
editor
Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].