The strongest signal in today's Doramagic GitHub metrics was not an abstract agent framework. It was a practical browser-verification pack:

https://github.com/tangweigang-jpg/doramagic-chrome-devtools-mcp-pack

In the 2026-05-20 sample, it had 120 clones, 60 unique cloners, and 44 views. The paths included traffic and commit-activity pages, which suggests readers were checking whether the pack was real enough to reuse.

That signal matters because AI coding agents often fail at the same boundary: they can edit code, but they cannot always prove that the browser experience works.

Common failure modes:

• the page is blank, but the agent says it is done;
• tests pass, but the button cannot be clicked;
• console errors are ignored;
• network failures are not connected to the code change;
• screenshots exist, but no acceptance criteria are checked.

Chrome DevTools MCP-style access gives an agent browser evidence: console output, network behavior, DOM state, and real interaction results.

But a tool is not yet a capability asset. A reusable pack should tell the host agent:

1. when browser evidence is required;
2. what evidence must be recorded;
3. when to stop instead of guessing;
4. how to connect browser failure back to a code change.

A useful loop looks like this:

open the target URL
-> inspect console errors
-> run the key interaction
-> record the visible result
-> compare against acceptance criteria
-> only then edit code or report success

This is an unofficial AI capability pack prepared by Doramagic. Unless the upstream project explicitly says otherwise, it is not an official upstream release.