chrome-devtools-axilisted

# Chrome DevTools AXI Answer the user's browser question with a reproducible observation, or complete the requested browser action and establish its result. This workflow needs an available shell, AXI and its runtime dependencies, and access to the selected target. ## Determine what would count as completion Identify the URL or existing tab, the question or action, and an observable success condition. Resolve available context before asking the user. Respect their chosen browser, tool, profile, and tab as well as any required host interface. Select ownership by the requested work: - General Chrome operation and live investigation belong here. - A static response that needs no browser state can be fetched directly. - Explicit Playwright investigation and existing Playwright tests belong to `playwright-testing`; harness installation or repair belongs to `setup-playwright`. - UI changes or a broader UX review need the relevant UI skill. Security audits need `security`. Add `tester-mindset` when the investigation needs a test strategy, rather than making these skills routine prerequisites. Use AXI as this package's execution interface. A missing executable is a capability gap to report, not a reason to switch to direct MCP automatically. An investigation request permits findings; source fixes, durable tests, and unrelated audits require that additional scope. ## Carry out a routine session 1. Discover the executable's version and help. Choose an installed command