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/leekjay/claude-skills-plugin/electron-webview-debuggingnpx skills add LeekJay/claude-skills-plugin --skill electron-webview-debugginggit 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/skills/leekjay/claude-skills-plugin/electron-webview-debugging)<a href="https://agentmods.dev/skills/leekjay/claude-skills-plugin/electron-webview-debugging"><img src="https://agentmods.dev/badge/skills/leekjay/claude-skills-plugin/electron-webview-debugging.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 | $0.00030 | $0.02073 |
| Opus 5 | $0.00015 | $0.01037 |
| Sonnet 5 | $0.00006 | $0.00415 |
| Haiku 4.5 | $0.00003 | $0.00207 |
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 4d 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Electron WebView Tag Debugging Skill
Decision Framework
Default behavior: For WebView debugging tasks, prefer Sub-Agent mode for systematic troubleshooting.
🔴 Mandatory Sub-Agent Triggers (ANY ONE triggers delegation)
- Unknown cause: WebView not working and cause is unclear (blank screen, crash, not loading)
- Multi-aspect debugging: Issue involves 2+ areas (IPC + events, preload + security, etc.)
- Security configuration: Any security-related WebView configuration review
- IPC communication issues: Debugging communication between main process and WebView
- Systematic investigation: Need to check configuration, events, and scripts together
- Crash/failure analysis: WebView crashes, freezes, or fails to load
- Preload script issues: Script injection not working, context isolation problems
- Performance debugging: WebView running slow, memory issues
🟢 Main Conversation Handling (ALL conditions must be met)
- Single aspect: Only checking one specific thing (e.g., "is this attribute correct?")
- Quick answer: Simple questions about WebView API or configuration
- Known fix: Already know what's wrong, just need syntax/usage help
- Documentation lookup: Just need to check how to use a specific API
Decision Flow
Check for ANY 🔴 mandatory trigger?
├─ YES → ✅ USE SUB-AGENT MODE immediately
│ subagent_type="electron-webview-debugging:electron-webview-debugging"
└─ NO → Check if ALL 🟢 simple conditions are met?
├─ YES → Handle in main conversation
└─ NO → ✅ USE SUB-AGENT MODE (default behavior)
Quick Reference Examples
| User Description | Trigger Signal | Decision |
|---|---|---|
| "WebView shows blank screen" | 🔴 Unknown cause | Sub-Agent |
| "How do I use executeJavaScript?" | 🟢 Documentation lookup | Main conversation |
| "WebView crashes when loading" | 🔴 Crash analysis | Sub-Agent |
| "Is this webpreferences correct?" | 🟢 Quick answer | Main conversation |
| "IPC messages not received" | 🔴 IPC communication issues | Sub-Agent |
| "What events can I listen to?" | 🟢 Documentation lookup | Main conversation |
| "Preload script not executing" | 🔴 Preload script issues | Sub-Agent |
| "Review WebView security config" | 🔴 Security configuration | Sub-Agent |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 260 lines · 30 tokens per session scan A eaa739c7794c
electron-webview-debugging is a skill published in the GitHub repository LeekJay/claude-skills-plugin (4 stars, last pushed 8mo ago), licensed MIT. It adds 30 tokens to every session and 2,073 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…