Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Browser Debug Agent

    1

    Connect to browser for testing like Claude Code but with headless mode and support for multiple engine (Chrome, Playwright, ...)

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    browser-debug-agent

    browser-debug-agent

    Example session with this skill installed

    The signup button on localhost:3000 isn't working on mobile. Check the console and fix the layout if it is overflowing.

    • Read your context and instructions
    • Compiled the browser-debug-agent

    I have reproduced the issue on localhost:3000 using a mobile viewport (375x812). The signup button was unreachable due to a container overflow and a script error.

    Debugging & Verification Results

    CheckViewportResultEvidence
    Console Errors375FAILUncaught ReferenceError: validateForm is not defined
    Layout Overflow375FAILscrollWidth (410) > clientWidth (375)
    Button Interaction375PASSClick event triggered after fix
    Responsive Check1280PASSNo layout regressions found

    Fixed Root Causes

    Script Error: The validateForm function was missing an export in utils/validation.js, preventing the click handler from executing.
    2.

    CSS Overflow: The signup container had a fixed width of 400px. Changed to max-width: 100% in SignupForm.module.css.

    Next steps

    1. Run the full Vitest suite to ensure no regressions in validation logic.
    2. Verify the fix on a physical iOS device to confirm touch target sizing.
    3. Merge the CSS change to the main branch.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Frontend debugging is expensive and slow when agents rely on constant screenshots. This skill implements a text-first evidence loop to repair browser-facing applications using the most efficient data available. It moves beyond code inspection by running the application to prove fixes through console logs, network states, and DOM geometry.

    What it does

    • Automated Reproduction creates a minimal test case before applying any code changes.
    • Evidence Hierarchy prioritizes console errors, network status, and DOM snapshots over expensive screenshots.
    • Layout Verification uses computed geometry to detect overflows and clipping without visual inspection.
    • Multi-Viewport Testing validates responsive behavior across desktop, tablet, and mobile breakpoints.
    • Cross-Runtime Support utilizes Playwright, Chrome DevTools Protocol, or project-specific tools based on availability.

    How it works

    1. Accept the bug report or verification task and define clear observable assertions.
    2. Reproduce the failure by navigating, acting, and recording the first divergence from expected behavior.
    3. Patch the root cause identified via console traces or network failures.
    4. Verify the fix using a multi-layer checklist covering functional, responsive, and accessibility requirements.

    Frameworks & tools

    This skill works with Playwright, Puppeteer, Chrome/Chromium CDP, and Obscura. It integrates with any frontend stack including React, Vue, and Next.js by interacting directly with the browser runtime.

    Why this beats prompting it yourself

    Standard prompts often cause agents to burn tokens on unnecessary screenshots or hallucinate layout fixes. This skill enforces a rigorous execution loop that requires browser-visible proof before claiming a task is complete.

    Use cases

    • Debugging uncaught JavaScript errors and failed API requests in the browser.
    • Fixing responsive layout bugs where elements overlap or overflow the viewport.
    • Performing automated QA smoke tests across multiple device resolutions.
    • Verifying accessibility roles and focus order via the DOM tree.

    Known limitations

    Requires shell access to run browser instances. It does not install new runtimes and relies on existing system or project dependencies.

    Requires shell access. Does not install runtimes. Limited to Chrome/Chromium for direct CDP. Authentication escalation requires explicit user approval.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Requires

    browser-debug-agent
    Node.js
    bda
    playwright
    Chrome Devtools MCP
    which

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Browser
    Network Access
    Environment Variables

    File Scopes

    browser-debug-agent-skill-main/**
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    Unlike standard agents that rely on expensive image processing, this skill uses a "text-first" loop prioritizing console logs, network states, and DOM geometry. This makes debugging significantly faster and more accurate while reducing token consumption.

    The skill is compatible with any agent capable of executing shell commands and supports Playwright, Puppeteer, and Chrome DevTools Protocol (CDP). It works across all frontend frameworks including React, Vue, and Next.js.

    The agent requires an environment where browser runtimes (like Chromium) are already installed and accessible via the shell. It does not install new binaries but rather interfaces with your existing project dependencies to run tests.

    You receive the optimized agent configuration, the multi-step execution logic for the evidence loop, and a set of predefined verification checklists for responsive and functional testing.

    Yes, the agent is designed for multi-viewport testing and uses computed geometry to detect layout issues like overflows or clipping across desktop, tablet, and mobile breakpoints without needing visual screenshots.

    New in Testing & Debugging