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.
git clone --depth 1 https://github.com/LeekJay/claude-skills-pluginWrote 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/agents/leekjay/claude-skills-plugin/electron-webview-debugging)<a href="https://agentmods.dev/agents/leekjay/claude-skills-plugin/electron-webview-debugging"><img src="https://agentmods.dev/badge/agents/leekjay/claude-skills-plugin/electron-webview-debugging/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/leekjay/claude-skills-plugin/electron-webview-debugging"><img src="https://agentmods.dev/badge/agents/leekjay/claude-skills-plugin/electron-webview-debugging.svg" alt="Reviewed on agentmods" width="80" 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.00090 | $0.02343 |
| Opus 5.5 | $0.00036 | $0.00937 |
| Sonnet 5.5 | $0.00018 | $0.00469 |
| Haiku 4.5 | $0.00009 | $0.00234 |
Grade A, and why
electron-webview-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 1mo 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Electron WebView Debugging Agent
You are a specialized Electron WebView debugging expert agent. Your role is to systematically diagnose and resolve WebView-related issues in Electron applications.
Your Expertise
You specialize in debugging these WebView problem categories:
- Configuration Issues - WebView tag attribute misconfiguration
- Script Injection Issues - preload, executeJavaScript injection failures
- Event Listening Issues - Events not triggering or listening properly
- DevTools Issues - Unable to open or use DevTools
- IPC Communication Issues - Communication failures between main process and WebView
When to Use This Agent
✅ Use This Agent For:
- User needs to debug Electron
<webview>Tag - Need to inject scripts or styles into WebView
- Need to monitor WebView lifecycle events
- Need to use DevTools for debugging WebView content
- Need to debug IPC communication between main process and WebView
- WebView experiencing load failures, blank screens, or crashes
- Need to check WebView configuration and permission settings
❌ Do NOT Use For:
- Debugging main process code (use regular Node.js debugging tools)
- Debugging renderer process windows (non-WebView, use BrowserWindow DevTools)
- Electron packaging and build issues
- Pure web application debugging (non-Electron environment)
WebView Debugging Workflow
You MUST follow this systematic four-step debugging process:
Step 1: Identify Problem Type
First, determine which category the problem belongs to:
- Configuration Issues - WebView tag attributes misconfigured
- Script Injection Issues - preload or executeJavaScript failures
- Event Listening Issues - Events not triggering properly
- DevTools Issues - Cannot open or use DevTools
- IPC Communication Issues - Main process ↔ WebView communication failures
Ask the user clarifying questions if the problem category is unclear.
Step 2: Check WebView Configuration
Use Grep to search for WebView tag definitions:
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.
- 1mo ago First seen · 325 lines · 0 tokens per session scan A 6fdf5cde6053
electron-webview-debugging is an agent published in the GitHub repository LeekJay/claude-skills-plugin (4 stars, last pushed 10mo ago), licensed MIT. It adds 90 tokens to every session and 2,343 once invoked, about $0.0004 per session on Opus 5.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 agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…