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 skills/delta-and-beta/electron-dev-bridge/electron-debuggingnpx skills add delta-and-beta/electron-dev-bridge --skill electron-debugginggit clone --depth 1 https://github.com/delta-and-beta/electron-dev-bridgeWhat 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.00066 | $0.01250 |
| Opus 5 | $0.00033 | $0.00625 |
| Sonnet 5 | $0.00013 | $0.00250 |
| Haiku 4.5 | $0.00007 | $0.00125 |
Grade A, and why
electron-debugging 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 2d 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Electron App Debugging with electron-dev-bridge
Systematic debugging using 41 MCP bridge tools.
Quick Diagnostic (3 calls)
# 1. What's on the page?
electron_get_page_summary
# 2. Any errors?
electron_get_errors
# 3. Any failed network requests?
electron_get_network_requests errorsOnly=true
If errors found, generate a full report: electron_error_report
Diagnostic Flowchart
Problem reported
|
+-- Can you connect?
| NO --> See "Connection Issues"
| YES
|
+-- Run electron_get_page_summary. Is UI visible?
| NO --> See "Blank Screen"
| YES
|
+-- Run electron_get_errors. Any exceptions?
| YES --> See "Error Analysis"
| NO
|
+-- Is the expected element present?
| NO --> See "Element Not Found"
| YES
|
+-- Does interaction work?
NO --> See "Interaction Failures"
YES --> Issue may be data-related. Check network + IPC.
Connection Issues
# Check port
electron_list_targets
# If no targets: app not running or wrong port
# Launch with auto-port (handles conflicts)
electron_launch appPath="/path/to/{YOUR_APP}"
# Or connect to specific port
electron_connect port=9230
| Error | Fix |
|---|---|
| Connection refused | Start app with --remote-debugging-port |
| Port in use | electron_launch auto-picks a free port |
| Wrong window | electron_list_targets then electron_switch_target |
| Connection lost | Auto-reconnects after 1s. If still down, electron_connect |
Blank Screen
electron_get_url
# Is the URL correct?
electron_wait_for_selector selector="{YOUR_APP_ROOT}" timeout=15000
# Did it appear?
electron_get_main_process_logs level="stderr"
# Any main process errors?
electron_get_console_logs level="error"
# Any renderer errors?
Error Analysis
# Grouped errors with stack traces
electron_get_errors
# Filter by source
electron_get_errors source="exception"
electron_get_errors source="network"
electron_get_errors source="console.error"
# Full error report (HTML dashboard)
electron_error_report
# Opens in browser — shows grouped errors, stack traces, timeline,
# failed requests, console errors, main process logs
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.
- 2d ago First seen · 203 lines · 66 tokens per session scan A 00f9a31759b0
electron-debugging is a skill published in the GitHub repository delta-and-beta/electron-dev-bridge (1 stars, last pushed 5mo ago), licensed MIT. It adds 66 tokens to every session and 1,250 once invoked, about $0.0003 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
node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol CLI.
version-upgrade
Prepare, validate, and publish a Rustwright version across the Python/PyPI and Node.js/npm packages. Use when asked to bump or upgrade the Rustwright version, prepare a release PR, tag a release, publish Rustwright, or verify both package registries.
chrome-agent
Local browser automation with structured, verified outcomes. Use for web navigation, scraping and extraction, form interaction, screenshots and downloads, network or console checks, responsive testing, or page-scoped device emulation.
scrape-structured-data
Get the repeating records off a web page (product grids, search results, job listings, news feeds, tables) as JSON, without writing CSS selectors and without spending a model call to read the HTML. Works on sites with no API, including ones behind a login or bot protection. Runs locally, one binary, no API key. Use…
owb
Open Web Bridge (OWB) — drive the user's own real browser with the owb command. Read pages behind their existing logins, gather and cross-check information, fill forms, walk multi-step flows, debug their site, audit responsive/accessibility behavior, and capture or reverse-engineer network traffic. Use this whenever…
bdg
Use bdg CLI for browser automation via Chrome DevTools Protocol. Provides direct CDP access (60+ domains, 300+ methods) for DOM queries, navigation, screenshots, network control, and JavaScript execution. Use this skill when you need to automate browsers, scrape dynamic content, or interact with web pages…