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 instructions/sergey-zededa/edgeviewlauncher/claude-mdgit 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/instructions/sergey-zededa/edgeviewlauncher/claude-md)<a href="https://agentmods.dev/instructions/sergey-zededa/edgeviewlauncher/claude-md"><img src="https://agentmods.dev/badge/instructions/sergey-zededa/edgeviewlauncher/claude-md.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.01924 | $0.01924 |
| Opus 5 | $0.00962 | $0.00962 |
| Sonnet 5 | $0.00385 | $0.00385 |
| Haiku 4.5 | $0.00192 | $0.00192 |
Grade A, and why
edgeViewLauncher CLAUDE.md 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 5d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Critical Rules
- NEVER DELETE KEYCHAIN ITEMS unless explicitly and unambiguously instructed for a specific item.
- NEVER create git tags or trigger release builds unless explicitly instructed.
- NEVER commit directly to
main. Always work on a feature branch and use PRs. - Do not modify
eve/— it contains reference implementations. - Do NOT include
Co-Authored-Byattribution in commit messages. - Always run tests and build after modifying code to verify changes.
Architecture
EdgeView Launcher is a Tauri v2 desktop app with three layers:
Tauri Core (Rust) — src-tauri/
Spawns Go backend as sidecar, creates windows, tray, and IPC commands.
All frontend API calls go through the generic api_call IPC command,
which proxies HTTP requests to the Go backend on a dynamic port.
Frontend (React + Vite) — frontend/
src/App.jsx: main UI — clusters, devices, tunnels, settings
src/tauriAPI.js: wraps all Tauri invoke() calls
src/components/TerminalView.jsx: xterm.js terminal over WebSocket
src/components/VncViewer.jsx: noVNC embedded viewer (overlay in main window)
vnc.html: standalone VNC window (separate Vite entry point, NOT in src/)
⚠️ vnc.html imports noVNC independently from VncViewer.jsx — both
must be kept in sync for any dependency or import changes.
Go Backend (sidecar) — cmd/edgeview-backend/
http-server.go: HTTP routes and WebSocket SSH terminal handler
app.go: business logic, ZEDEDA API integration, session management
internal/config/: cluster config persistence (~/.edgeview-config.json)
internal/session/: EdgeView session cache, TCP tunnel management
internal/ssh/: SSH key generation (~/.ssh/edgeview_rsa)
internal/zededa/: ZEDEDA Cloud API client
Data flow: React → tauriAPI.js (invoke) → Rust api_call command → HTTP to Go backend on localhost:<dynamic-port>. The port is discovered at startup by parsing the Go backend's stdout log line "HTTP Server starting on :<PORT>".
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.
- 5d ago First seen · 127 lines · 1,924 tokens per session scan A 1fb13d35a56f
edgeViewLauncher CLAUDE.md is an instructions file published in the GitHub repository sergey-zededa/edgeViewLauncher (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 1,924 tokens to every session, about $0.0096 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).