visual-debugging

visual-debugging is a skill for Claude Code, Codex from Akakaui/visual-browser-agent. It costs 19 tokens per session (729 once invoked), scanned A, original, MIT.

A method for finding and explaining visual problems in a website or application by capturing screenshots, inspecting page structure and styles, and comparing states. It covers issues such as layout, rendering, and animation.

In plain words
What is it for?
Use it to investigate overlapping or misaligned elements, browser and viewport differences, CSS conflicts, image or font problems, and animation glitches.
Why use it?
It replaces guesswork with visual evidence and information about the page’s HTML and CSS. It helps connect what users see with browser errors or network problems.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to investigate overlapping or misaligned elements, browser and viewport differences, CSS conflicts, image or font problems, and animation glitches.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/akakaui/visual-browser-agent/visual-debugging
Install

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.

Any agent
npx skills add Akakaui/visual-browser-agent --skill visual-debugging
Clone the repo
git clone --depth 1 https://github.com/Akakaui/visual-browser-agent

Made for: Claude Code, Codex.

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 visual-debugging

README.md
[![agentmods](https://agentmods.dev/badge/skills/akakaui/visual-browser-agent/visual-debugging/github.svg)](https://agentmods.dev/skills/akakaui/visual-browser-agent/visual-debugging)
Your own site
<a href="https://agentmods.dev/skills/akakaui/visual-browser-agent/visual-debugging"><img src="https://agentmods.dev/badge/skills/akakaui/visual-browser-agent/visual-debugging/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.

agentmods 80×15 button for visual-debugging

Your own site · 80×15
<a href="https://agentmods.dev/skills/akakaui/visual-browser-agent/visual-debugging"><img src="https://agentmods.dev/badge/skills/akakaui/visual-browser-agent/visual-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 729 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.
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.00019 $0.00729
Opus 5.5 $0.00008 $0.00292
Sonnet 5.5 $0.00004 $0.00146
Haiku 4.5 $0.00002 $0.00073

Measured 1mo ago against content hash 307ee8f06552, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

visual-debugging 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 1mo 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.

skills/visual-debugging/SKILL.md · 121 lines

How it starts

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

Visual Debugging Skill

When to Use

Use this skill to debug visual issues:

  • Layout breaks (overflow, overlap, misalignment)
  • Rendering differences across browsers/viewports
  • CSS specificity/conflict issues
  • Z-index problems
  • Flexbox/Grid layout bugs
  • Image loading/aspect ratio issues
  • Font rendering problems
  • Animation glitches

Instructions

Reproduction

  1. navigate to problematic page/state
  2. inspect_page to get DOM/CSS context
  3. capture_screenshot of issue
  4. If intermittent: record_interaction to capture occurrence

Comparison

For cross-browser/viewport issues:

  1. Test in each target environment
  2. Capture same view in each
  3. Use review_visual_evidence with multiple artifacts
  4. Document differences

State Comparison

For before/after or interaction-triggered bugs:

  1. Capture "before" state
  2. Trigger interaction
  3. Capture "after" state
  4. Compare via vision review

CSS Analysis

From inspect_page accessibility tree + DOM:

  1. Identify problematic element
  2. Extract computed styles (via CDP if needed)
  3. Check: box model, flex/grid properties, positioning, z-index

Console/Network Correlation

  1. Check console errors during reproduction
  2. Check network for failed resources (fonts, images, CSS)
  3. Correlate with visual symptoms

Debugging Workflow

1. Reproduce → capture evidence
2. Isolate → minimal test case
3. Hypothesize → check CSS/DOM
4. Verify → fix attempt → recapture
5. Confirm → document

Output

# Visual Debug Report: {issue}

## Environment
- URL: {url}
- Viewport: {viewport}
- Browser: {browser}
- Steps to reproduce: {steps}

## Evidence
- Before: {screenshot}
- After: {screenshot}
- Recording: {clip}

## Analysis
- Root cause: {CSS/JS/Asset/Environment}
- Affected elements: {selectors}
- Computed styles: {key properties}

## Fix Recommendation
{code snippet or description}

## Verification
- Fixed in: {environments}
- Evidence: {post-fix screenshots}

Safety

  • Don't modify page state destructively
  • Only capture, don't inject code (unless explicitly allowed)
  • Respect private/authenticated pages

Read the full file on GitHub · 121 lines

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. 1mo ago First seen · 121 lines · 19 tokens per session scan A 307ee8f06552

Subscribe to this mod's changes

visual-debugging is a skill published in the GitHub repository Akakaui/visual-browser-agent (0 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 729 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

rmyndharis/antigravity-skills · 36 tokens

cwv-optimizer

Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…

adobe/skills · 112 tokens