browser-trace SKILL.md skillB
browser-trace from vanducng/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vanducng/skills/browser-trace@git:20260911.9e58ef3Pins git:20260911.9e58ef3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vanducng/skills
- Path
skills/browser-trace/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260911.9e58ef3, committed Sep 11, 2026
- First version recorded
- May 20, 2026
- Size
- 11,482 bytes
- Repository stars
- 8
- License
- MIT
Capture a full DevTools-protocol trace of a locally driven browser automation - CDP firehose, screenshots, and DOM dumps - then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress local session, or feed structured per-page summaries back into an agent loop so its next iteration learns from the last one.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Browser Trace Attach a **second, read-only CDP client** to a browser session that is already being driven by your main automation. The trace records the full DevTools firehose to NDJSON, polls for screenshots and DOM dumps in parallel, and slices everything into a directory tree that bash tools can search. This skill does **not** drive pages - it only listens. Pair it with `agent-browser` (the primary local driver, attached via `agent-browser connect <port>`), Playwright, Stagehand, or anything else that speaks CDP. ## When to use - The user wants to debug a browser-automation run (failing form, missing element, hung navigation, JS exception). - The user has a running automation and wants to attach a trace mid-flight without restarting it. - The user wants to split a CDP firehose into network / console / DOM / page buckets. - The user wants screenshots + DOM snapshots over time, joined to CDP events by timestamp. If the user just wants to **drive** the browser, use the `agent-browser` skill instead. ## Setup check ```bash node --version # require Node 18+ (built-in WebSocket) …
Read the whole file at its exact version.
How to install
mdr add vanducng/skills/browser-trace@sha256:b669b1d81f80d836The line at the top of this page pins the label git:20260911.9e58ef3, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_owsuftupofu4hzfk)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 20, 2026 and Sep 11, 2026, about one every 28 days. Its first recorded version is graded A and its latest B.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260911.9e58ef3 latest | 2026-09-11 | 9e58ef3 | 11,482 B | B | view · diff |
| git:20260724.51405ee | 2026-07-24 | 51405ee | 16,494 B | B | view · diff |
| git:20260614.560f72b | 2026-06-14 | 560f72b | 15,609 B | A | view · diff |
| git:20260605.94e83d0 | 2026-06-05 | 94e83d0 | 15,303 B | A | view · diff |
| git:20260520.c817083 | 2026-05-20 | c817083 | 15,024 B | A | view |
Audit of the latest version
- fail: No link to a raw IP address (matched: http://127.0.0.1:9222)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11482 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
vanducng/skills · 8 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_owsuftupofu4hzfk GET https://markdownregistry.com/api/v1/resolve?ref=vanducng/skills/browser-trace GET https://markdownregistry.com/api/v1/blob/b669b1d81f80d8361fa326b1004a83c784e23961be259f3855348d783ca3c0cb
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.