ui-debug-workflow

ui-debug-workflow is a skill for Claude Code from pantheon-org/tekhne. It costs 72 tokens per session (1,030 once invoked), scanned A, original, MIT.

A repeatable process for investigating user-interface bugs with screenshots, page structure, and browser logs as evidence. It compares the original and changed behavior under the same conditions before a fix is accepted.

In plain words
What is it for?
Use it to reproduce frontend bugs, verify visual changes, collect browser evidence, and create reports for stakeholders.
Why use it?
It helps distinguish real visual regressions from differences caused by viewport, data, animations, or other test conditions.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is sh skills/agentic-harness/skill-quality-auditor/scripts/evaluate.sh ui-debug-workflow --json.

Good fit Use it to reproduce frontend bugs, verify visual changes, collect browser evidence, and create reports for stakeholders.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/pantheon-org/tekhne
agentmods
npx agentmods add skills/pantheon-org/tekhne/ui-debug-workflow

Made for: Claude Code.

Wrote 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.

agentmods badge for ui-debug-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/pantheon-org/tekhne/ui-debug-workflow.svg)](https://agentmods.dev/skills/pantheon-org/tekhne/ui-debug-workflow)
Your own site
<a href="https://agentmods.dev/skills/pantheon-org/tekhne/ui-debug-workflow"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/ui-debug-workflow.svg" alt="Measured on agentmods" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,030 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium MCP Rug Pull · line 42
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 92
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00072 $0.01030
Opus 5 $0.00036 $0.00515
Sonnet 5 $0.00014 $0.00206
Haiku 4.5 $0.00007 $0.00103

Measured 4d ago against content hash 61c969cf89f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

ui-debug-workflow 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 4d ago.

The scan reads SKILL.md. This mod also ships 4 executable files (references/ui-debug-test.spec.ts, scripts/capture-evidence.sh, scripts/compare-evidence.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/testing/ui-debug-workflow/SKILL.md · 146 lines

How it starts

The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.

UI Debug Workflow

When to Use

Use this skill when frontend behavior must be verified with reproducible evidence.

When Not to Use

Do not use this workflow for backend-only issues with no UI symptom.

Core Principles

  1. Reproduce first, then modify code.
  2. Capture baseline and changed evidence under the same conditions.
  3. Compare artifacts before declaring a fix.
  4. Document commands, environment, and outcomes.

Deterministic Workflow

  1. Capture baseline evidence from a known branch.
  2. Apply fix and capture changed evidence with identical steps.
  3. Compare screenshots, DOM, and logs.
    • If comparison shows unexpected differences: 1) verify identical conditions (URL, viewport, seed data, build mode) 2) check for flaky or animated elements 3) re-capture both runs if needed before concluding.
  4. Record pass/fail outcomes and unresolved risks.
  5. Publish a concise report with links to artifacts.

Quick Commands

Install browser runtime for automation

npx playwright install chromium

Expected result: Chromium runtime is available for automated UI checks.

Capture baseline evidence

./skills/ui-debug-workflow/scripts/capture-evidence.sh baseline http://localhost:3000 ./baseline

Expected result: screenshots, DOM snapshots, and logs saved in ./baseline.

Capture changed evidence

./skills/ui-debug-workflow/scripts/capture-evidence.sh changed http://localhost:3000 ./changed

Expected result: comparable artifacts saved in ./changed.

Compare baseline vs changed artifacts

./skills/ui-debug-workflow/scripts/compare-evidence.sh ./baseline ./changed ./comparison.md

Expected result: comparison.md with summarized differences.

Run end-to-end debug session

./skills/ui-debug-workflow/scripts/full-debug-session.sh main fix/my-branch http://localhost:3000 "npm run build" "npm start"

Expected result: complete session output with report-ready evidence.

Evaluate this skill quality

Read the full file on GitHub · 146 lines

Files

What ships with it

38 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.

Changes

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.

  1. 4d ago First seen · 146 lines · 72 tokens per session scan A 61c969cf89f7

Subscribe to this mod's changes

ui-debug-workflow is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 1,030 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-09-03.