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/sergey-zededa/edgeviewlauncher/debugging_connectionsnpx skills add sergey-zededa/edgeViewLauncher --skill debugging_connectionsgit clone --depth 1 https://github.com/sergey-zededa/edgeViewLauncherWrote 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/sergey-zededa/edgeviewlauncher/debugging_connections)<a href="https://agentmods.dev/skills/sergey-zededa/edgeviewlauncher/debugging_connections"><img src="https://agentmods.dev/badge/skills/sergey-zededa/edgeviewlauncher/debugging_connections.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.00027 | $0.00997 |
| Opus 5 | $0.00014 | $0.00498 |
| Sonnet 5 | $0.00005 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
Debugging Connections 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging EdgeView Launcher Connections (SSH, VNC, TCP Tunnels)
This skill provides context and steps for troubleshooting communication issues between the EdgeView Launcher application, the local proxy (internal/session/manager.go), and ZEDEDA EdgeView service.
1. Comparing with Reference Implementations
If connection stability (e.g., stalling, dropping, "TCP EOF") is observed, the primary source of truth is the reference implementation: eve/edgeview-client.
- Check
eve/edgeview-clientsource code for SSH connection management, keep-alive mechanisms, and WebSocket protocol implementation. - Compare these mechanisms with our application's
internal/session/manager.goandinternal/zededa/client.go. - Identify discrepancies or missing keep-alive/handshake logic.
2. Inspecting TCP Tunnel Data Flow
- Issues with data flow ("TCP EOF", client disconnected) often stem from early termination of the tunnel handshake.
- Look at the
MappingIDallocation and verification. - Add minimal, precise debug logging near the EOF conditions to trace the problem without spamming the console with verbose API logs.
3. SSH Terminal-Specific Issues
- Stalling/Dropping: Verify WebSocket pings are sent consistently, similar to the reference implementation. Verify "No password provided" or "invalid packet length" errors to ensure the SSH payload is correctly wrapped.
- Rendering & Resizing:
- Ensure ANSI color codes are intact when passing through the WebSocket to
xterm.js. - Check dynamic resizing: Confirm the terminal window dimensions (e.g., 120x80) synchronize with the remote PTY size via resizing events from the frontend to the backend.
- Ensure ANSI color codes are intact when passing through the WebSocket to
4. VNC-Specific Issues
- External Clients (e.g., RealVNC): External VNC viewers might enforce stricter protocol handshake timings. Check for "no device online" errors resulting from early closure by the edge.
- noVNC Built-in Viewer: The built-in viewer might have helpers (like the on-screen keyboard) to send special key combinations. Test this client first as a baseline before debugging external clients.
- Review keep-alive logic inside
manager.gospecific to VNC proxying.
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 · 53 lines · 27 tokens per session scan A 40f8ae7f7b1f
Debugging Connections is a skill published in the GitHub repository sergey-zededa/edgeViewLauncher (5 stars, last pushed 9d ago), licensed Apache-2.0. It adds 27 tokens to every session and 997 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…