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.
git clone --depth 1 https://github.com/pantheon-org/tekhnenpx agentmods add skills/pantheon-org/tekhne/ui-debug-workflowWrote 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/pantheon-org/tekhne/ui-debug-workflow)<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>- NVIDIA SkillSpector warn
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]
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.00072 | $0.01030 |
| Opus 5 | $0.00036 | $0.00515 |
| Sonnet 5 | $0.00014 | $0.00206 |
| Haiku 4.5 | $0.00007 | $0.00103 |
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.
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 — 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
- Reproduce first, then modify code.
- Capture baseline and changed evidence under the same conditions.
- Compare artifacts before declaring a fix.
- Document commands, environment, and outcomes.
Deterministic Workflow
- Capture baseline evidence from a known branch.
- Apply fix and capture changed evidence with identical steps.
- 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.
- Record pass/fail outcomes and unresolved risks.
- 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
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.
- .audits/2026-02-21/analysis.md 8.1 KB
- .audits/2026-02-21/audit.json 142 B
- .audits/2026-02-21/remediation-plan.md 230 B
- .audits/2026-02-22/analysis.md 8.1 KB
- .audits/2026-02-22/audit.json 142 B
- .audits/2026-02-22/remediation-plan.md 230 B
- .audits/2026-02-23/analysis.md 8.1 KB
- .audits/2026-02-23/audit.json 143 B
- .audits/2026-02-23/remediation-plan.md 226 B
- .audits/2026-03-02/analysis.md 1.0 KB
- .audits/2026-03-02/audit.json 416 B
- .audits/2026-03-02/remediation-plan.md 1.7 KB
- .audits/latest 10 B
- .tessl-plugin/plugin.json 507 B
- CHANGELOG.md 374 B
- evals/scenario-01.md 2.8 KB
- evals/scenario-02.md 3.1 KB
- evals/scenario-03.md 2.8 KB
- evals/scenario-04.md 2.7 KB
- evals/scenario-05.md 2.5 KB
- references/agent-browser-browser-automation.md 3.9 KB
- references/agent-browser-not-found-troubleshooting.md 1.1 KB
- references/blank-screenshots-troubleshooting.md 1.1 KB
- references/browser-devtools-guide.md 702 B
- references/comprehensive-template-reporting.md 4.1 KB
- references/debugging-checklist.md 657 B
- references/dom-snapshots-evidence-collection.md 1.9 KB
- references/evidence-templates.md 632 B
- references/git-context-evidence-collection.md 1.8 KB
- references/INSTALL-SUMMARY.md 10 KB
- references/logs-evidence-collection.md 2.3 KB
- references/playwright-testing-browser-automation.md 5.2 KB
- references/programmatic-selection-troubleshooting.md 1.9 KB
- references/screenshots-evidence-collection.md 1.7 KB
- references/ui-debug-test.spec.ts 11 KB runs code
- scripts/capture-evidence.sh 5.4 KB runs code
- scripts/compare-evidence.sh 5.8 KB runs code
- scripts/full-debug-session.sh 6.0 KB runs code
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.
- 4d ago First seen · 146 lines · 72 tokens per session scan A 61c969cf89f7
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.
Other skills, from other repositories
fixing-motion-performance
Audit and fix animation performance issues including layout thrashing, compositor properties, scroll-linked motion, and blur effects. Use when animations stutter, transitions jank, or reviewing CSS/JS animation performance.
frontend-visual-verification
Confirm a CSS/HTML/template change actually rendered in a running browser — without being fooled by stale browser cache. Use whenever you edited frontend code (CSS, EJS/HTML, components) and must verify the visual result, especially when a vision screenshot seems to contradict the DOM or the served asset.
implementation-debugging
Use when animation doesn't work as expected, has bugs, or behaves inconsistently.
performance-optimization
Use when animation runs slow, janky, or causes frame drops.
inspecting-hermes-desktop-dom
When you are developing apps/desktop and the user is running that same app (hgui / npm run dev), you can read the live rendered DOM of the window they are looking at — computed styles, geometry, which CSS rule actually won, console output — instead of inferring it from .tsx and being wrong.
inspecting-hermes-desktop-dom
Read the live Hermes desktop DOM/CSS over CDP.