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 skills add AxGord/claude-workflow --skill debug-bridge-scaffoldgit clone --depth 1 https://github.com/AxGord/claude-workflowWrote 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/skills/axgord/claude-workflow/debug-bridge-scaffold)<a href="https://agentmods.dev/skills/axgord/claude-workflow/debug-bridge-scaffold"><img src="https://agentmods.dev/badge/skills/axgord/claude-workflow/debug-bridge-scaffold.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.1 | $0.00016 | $0.00761 |
| Opus 5 | $0.00008 | $0.00380 |
| Sonnet 5 | $0.00003 | $0.00152 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
debug-bridge-scaffold 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 7d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Bridge Scaffold
When to Use
When you need runtime inspection of an application built with a technology that has no existing debug bridge.
Step 1: Check Existing Solutions First
Before building a custom bridge, check if a standard tool already works:
| Technology | Existing Solution |
|---|---|
| Web/Electron/browser apps | Playwright MCP, browser DevTools |
| Native apps with standard UI toolkit | Accessibility API MCP |
| Any app with visible UI | Computer Use (screenshot + click) |
| OpenFL/hxcpp | debug-bridge-openfl skill (already exists) |
If an existing solution covers your needs — use it. Don't build a bridge.
Step 2: Build a Custom Bridge
If no existing tool works, create an HTTP bridge following this pattern:
Architecture
[Background Thread] HTTP Server (127.0.0.1:PORT)
↓ accept()
[Worker Thread] Parse request → dispatch to main thread
↓ runOnMainThread(fn)
[Main Thread] Execute handler → return result
↑ result via Lock/Mutex
[Worker Thread] Send HTTP response
Required Endpoints
| Endpoint | Method | Purpose |
|---|---|---|
/ping |
GET | Health check |
/screenshot |
GET | Capture visual state → save to /tmp → return path |
/shutdown |
POST | Graceful exit |
Framework-Specific Endpoints
Add endpoints relevant to the technology:
- UI frameworks: display tree, component inspection, event simulation
- Game engines: scene graph, entity list, physics state
- Servers: request log, connection pool, cache state
Implementation Checklist
- HTTP server on background thread (127.0.0.1 only — no external access)
- Main-thread dispatch for all UI/rendering operations
- JSON envelope:
{"ok": true, "data": ...}/{"ok": false, "error": "..."} - Conditional compilation (only in debug builds)
- Graceful shutdown (close socket, flush stdout, exit)
Step 3: Create a Tech-Specific Skill
After building the bridge, create ~/.claude/skills/debug-bridge-<tech>/SKILL.md with:
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.
- 7d ago First seen · 99 lines · 16 tokens per session scan A 98e8ea8ff55d
debug-bridge-scaffold is a skill published in the GitHub repository AxGord/claude-workflow (5 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 761 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.