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 delta-and-beta/electron-dev-bridge --skill electron-e2e-testinggit clone --depth 1 https://github.com/delta-and-beta/electron-dev-bridgeWrote 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/delta-and-beta/electron-dev-bridge/electron-e2e-testing)<a href="https://agentmods.dev/skills/delta-and-beta/electron-dev-bridge/electron-e2e-testing"><img src="https://agentmods.dev/badge/skills/delta-and-beta/electron-dev-bridge/electron-e2e-testing.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.00060 | $0.01042 |
| Opus 5 | $0.00030 | $0.00521 |
| Sonnet 5 | $0.00012 | $0.00208 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade A, and why
electron-e2e-testing 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 6d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Electron E2E Testing with electron-dev-bridge
Structured test patterns using the MCP bridge. 41 tools available.
Test Pattern: Batch Execute + Assert
The fastest pattern — combine actions and verification in minimal calls:
# 1. Connect
electron_connect
# 2. Understand the page
electron_get_page_summary
# 3. Snapshot before action
electron_diff_state mode="snapshot"
# 4. Execute steps in one call
electron_execute_steps steps=[
{"wait": "[data-testid='form']"},
{"fill": {"selector": "#email", "text": "[email protected]"}},
{"fill": {"selector": "#name", "text": "Jane Doe"}},
{"click": "[type='submit']"},
{"wait": ".success-message"},
{"screenshot": true}
]
# 5. Assert results
electron_assert assertions=[
{"selector": ".success-message", "text": "Saved"},
{"selector": "#email", "value": "[email protected]"},
{"url": "/dashboard"}
]
# 6. Check what changed
electron_diff_state mode="diff"
Playbook: Form Fill & Submit
# 1. Discover form structure
electron_get_form_state selector="form"
# 2. Fill all fields in one batch
electron_execute_steps steps=[
{"fill": {"selector": "#name", "text": "Jane Doe"}},
{"fill": {"selector": "#email", "text": "[email protected]"}},
{"click": "[type='submit']"}
]
# 3. Wait for response
electron_wait_for_network_idle idleTime=500
# 4. Assert
electron_assert assertions=[
{"selector": ".success", "text": "submitted"},
{"selector": ".error", "exists": false}
]
Playbook: Visual Regression
# Phase 1: Capture baseline
electron_connect
electron_wait_for_selector selector="{YOUR_APP_ROOT}"
electron_screenshot
# Note the returned file path as baseline
# Phase 2: After code changes, restart
electron_launch appPath="/path/to/{YOUR_APP}"
electron_wait_for_selector selector="{YOUR_APP_ROOT}"
electron_screenshot
# Note the returned file path as current
# Phase 3: Compare
electron_compare_screenshots pathA="baseline.png" pathB="current.png"
# Returns: { identical: false, diffPercent: 0.5, totalBytes: 120000, diffBytes: 600 }
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.
- 6d ago First seen · 147 lines · 60 tokens per session scan A 795409b121eb
electron-e2e-testing is a skill published in the GitHub repository delta-and-beta/electron-dev-bridge (1 stars, last pushed 5mo ago), licensed MIT. It adds 60 tokens to every session and 1,042 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
browser4-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.