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/guyroyse/mesh-browser/claude-mdgit clone --depth 1 https://github.com/guyroyse/mesh-browserWhat 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.01562 | $0.01562 |
| Opus 5 | $0.00781 | $0.00781 |
| Sonnet 5 | $0.00312 | $0.00312 |
| Haiku 4.5 | $0.00156 | $0.00156 |
Grade B, and why
mesh-browser CLAUDE.md scanned grade B with 1 finding 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 3d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
const response = await fetch('http://localhost:PORT/proxy/reticulum', { method: 'POST', How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
AI assistant context for MeshBrowser development.
Project Overview
MeshBrowser is an Electron-based desktop browser for decentralized protocols, currently supporting Reticulum mesh networking via the rweb:// protocol scheme. Future protocols include IPFS and Hypercore.
Key Goals:
- Web-like browsing experience over mesh networks
- Familiar browser interface (address bar, navigation, status indicators)
- No configuration needed - auto-discovery and mesh routing
- Extensible architecture for multiple decentralized protocols
Architecture
High-Level Design
Electron Frontend ↔ HTTP API ↔ Python Backend (Reticulum)
- Frontend: Electron with electron-vite and TypeScript, custom protocol handlers for
rweb://URLs - Communication: HTTP for data requests, stdio for process lifecycle
- Backend: Python process with ThreadingHTTPServer + Reticulum networking
File Structure
src/
├── main/ # Electron main process
│ ├── main.ts # App entry, lifecycle management
│ ├── config.ts # Environment detection, paths
│ ├── windows.ts # Window/view creation, IPC handlers, view events
│ └── processes.ts # Python backend process instance
├── preload/
│ └── preload.ts # Context bridge for renderer ↔ main IPC
├── protocol-handlers/
│ ├── protocol-schemes.ts # Protocol registration (rweb://)
│ └── rweb-handler.ts # Protocol handler implementation
├── renderer/ # Multi-view UI (navigation, content, status)
│ ├── navigation/ # Address bar + nav buttons
│ │ ├── index.html
│ │ ├── navigation.ts
│ │ └── navigation.css
│ ├── status/ # Status indicators
│ │ ├── index.html
│ │ ├── status.ts
│ │ └── status.css
│ ├── shared/ # Common styles, assets
│ │ ├── common.css
│ │ └── assets/
│ └── types/
│ └── window.d.ts # BrowserAPI type declarations
├── http-process/ # Backend process lifecycle management
│ ├── manager.ts # HttpProcessManager
│ ├── starter.ts # Process startup
│ ├── stopper.ts # Process shutdown
│ └── message-handler.ts # Lifecycle event monitoring
└── python/ # Python backend
├── main.py # Entry point
├── console/ # Process lifecycle (STARTUP signals, structured logging)
├── http_api/ # HTTP server
│ ├── server.py # ThreadingHTTPServer wrapper
│ └── handler.py # Request handlers
└── reticulum/ # Reticulum networking (6 modules)
├── client.py # ReticulumClient coordinator
├── url.py # URL parsing
├── link.py # RNS link management
├── fetch.py # Content fetching
├── response.py # Response parsing
└── status.py # Network status
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.
- 3d ago First seen · 174 lines · 1,562 tokens per session scan B 3486e2dd4cd4
mesh-browser CLAUDE.md is an instructions file published in the GitHub repository guyroyse/mesh-browser (11 stars, last pushed 3d ago), licensed MIT. It adds 1,562 tokens to every session, about $0.0078 per session on Opus 5. A static security scan graded it B with 1 finding (sends data to an external url). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.