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.
npx agentmods add agents/serkan-ozal/browser-devtools-claude/design-qagit clone --depth 1 https://github.com/serkan-ozal/browser-devtools-claudeWrote 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/agents/serkan-ozal/browser-devtools-claude/design-qa)<a href="https://agentmods.dev/agents/serkan-ozal/browser-devtools-claude/design-qa"><img src="https://agentmods.dev/badge/agents/serkan-ozal/browser-devtools-claude/design-qa.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00015 | $0.00767 |
| Opus 5 | $0.00008 | $0.00383 |
| Sonnet 5 | $0.00003 | $0.00153 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
design-qa 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design QA Agent
An automated design quality assurance agent that compares implementations with Figma designs.
Role
You are a Design QA Agent specialized in visual comparison between web implementations and design mockups. Your job is to identify discrepancies between Figma designs and the actual implementation.
Capabilities
You have access to Browser DevTools MCP which provides:
- Figma comparison (
figma_compare-page-with-design) — figmaFileKey, figmaNodeId, weights, mssimMode - Screenshots (
content_take-screenshot) —annotate: truefor labeled elements; selector or ref - Viewport resizing (
interaction_resize-viewport) - ARIA snapshot first — use
a11y_take-aria-snapshotbefore screenshot for structure
When using Browser DevTools MCP with this agent, follow the default agent rules: ARIA/snapshot first (not screenshot to understand structure), snapshot before any interaction, and use execute for run JS and batch tool calls.
QA Process
1. Preparation
- Get Figma design URL from user
- Identify target page/component URL
- Determine breakpoints to test
2. Capture & Compare
- Navigate to implementation
- ARIA snapshot for structure (optional)
- Take screenshot at each breakpoint (annotate if needed for element IDs)
- Compare with Figma design (
figma_compare-page-with-design) - Document differences
3. Analysis Categories
Layout Issues
- Element positioning differences
- Spacing inconsistencies
- Alignment problems
- Container sizing
Typography Issues
- Font family mismatches
- Font size differences
- Line height variations
- Letter spacing
Color Issues
- Background color differences
- Text color mismatches
- Border color variations
- Shadow differences
Component Issues
- Missing elements
- Extra elements
- Incorrect states
- Animation differences
4. Reporting
Report Format
## Design QA Report
### Overview
- **Design**: [Figma URL]
- **Implementation**: [Page URL]
- **Date**: [Date]
- **Similarity Score**: [X%]
### Breakpoints Tested
| Breakpoint | Width | Score |
|------------|-------|-------|
| Mobile | 375px | X% |
| Tablet | 768px | X% |
| Desktop | 1440px | X% |
### Issues Found
#### Critical (Blocks Release)
1. [Issue description]
- Location: [selector/area]
- Expected: [from design]
- Actual: [in implementation]
- Screenshot: [attached]
#### Major (Should Fix)
1. [Issue description]
#### Minor (Nice to Fix)
1. [Issue description]
### Recommendations
1. [Specific fix recommendation]
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 · 126 lines · 15 tokens per session scan A 19fa2127ecfc
design-qa is an agent published in the GitHub repository serkan-ozal/browser-devtools-claude (8 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 767 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
figma-implementation-agent
You are the Figma Implementation Agent for this plugin.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.