Browser Debugging SKILL.md skillB
Browser Debugging from nxtg-ai/forge-plugin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nxtg-ai/forge-plugin/Browser Debugging@git:20261007.1acb8b5Pins git:20261007.1acb8b5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nxtg-ai/forge-plugin
- Path
plugins/nxtg-forge/skills/browser-debugging/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261007.1acb8b5, committed Oct 7, 2026
- First version recorded
- Feb 7, 2026
- Size
- 9,014 bytes
- Repository stars
- 6
- License
- MIT
Debug the running NXTG-Forge web dashboard by driving a headless Chromium via the Playwright MCP server — read console errors, take screenshots, inspect the DOM accessibility tree, and watch network requests. Use when the dashboard renders blank or broken after a UI change, when the user reports browser console errors, after fixing a React bug (infinite loop, "Maximum update depth", stale state) to confirm it's gone, or when verifying a visual/interactive change…
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 Debugging Skill
Drive a real (headless) Chromium against the running NXTG-Forge dashboard from inside
Claude Code, using the **Playwright MCP** server. No Windows Chrome dependency — Playwright
launches its own headless Chromium inside WSL.
## Where the tools come from (read first)
The Playwright MCP server is registered in **`forge-ui/.mcp.json`**, NOT in the plugin's
`.mcp.json` (which only registers governance / orchestrator / semgrep). The `browser_*` tools
only exist when a Claude Code session has `forge-ui/.mcp.json` loaded — i.e. you are working in
the `forge-ui/` repo. From the plugin repo alone they are unavailable. Config as shipped:
```jsonc
"playwright": { "command": "npx", "args": ["@playwright/mcp@latest", "--headless", "--console-level", "debug"] }
```
Two consequences of that exact config:
- `--console-level debug` → `browser_console_messages` returns **verbose debug logs**, not just
errors. Filter for `error`/`warning` yourself; do not assume a clean-looking tail means no errors.
- **No `--caps`** flag → the `pdf`, `vision` (coordinate clicks/screenshots), and `devtools`
…Read the whole file at its exact version.
How to install
mdr add nxtg-ai/forge-plugin/Browser Debugging@sha256:a12bcb1d30e5f565The line at the top of this page pins the label git:20261007.1acb8b5, 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_p64px4wvk5c2kyra)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Feb 7, 2026 and Oct 7, 2026, about one every 121 days. Its first recorded version is graded A and its latest B.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.1acb8b5 latest | 2026-10-07 | 1acb8b5 | 9,014 B | B | view · diff |
| git:20260714.4fd0952 | 2026-07-14 | 4fd0952 | 7,510 B | A | view · diff |
| git:20260207.88c1f6e | 2026-02-07 | 88c1f6e | 3,930 B | A | view |
Audit of the latest version
- fail: No link to a raw IP address (matched: http://127.0.0.1:5051)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9014 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
nxtg-ai/forge-plugin · 6 stars · license MIT · pushed 2026-10-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_p64px4wvk5c2kyra GET https://markdownregistry.com/api/v1/resolve?ref=nxtg-ai/forge-plugin/Browser Debugging GET https://markdownregistry.com/api/v1/blob/a12bcb1d30e5f5658d768bb9bf8c5c2665167357aa96a6fcd4dbbba73839ee99
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.