Borrowing it
Nothing to install: this file belongs to pouriamrt/claude-mesh. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pouriamrt/claude-mesh/main/CLAUDE.mdgit clone --depth 1 https://github.com/pouriamrt/claude-meshWrote 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/pouriamrt/claude-mesh/claude-md)<a href="https://agentmods.dev/instructions/pouriamrt/claude-mesh/claude-md"><img src="https://agentmods.dev/badge/instructions/pouriamrt/claude-mesh/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.1 | $0.01774 | $0.01774 |
| Opus 5 | $0.00887 | $0.00887 |
| Sonnet 5 | $0.00355 | $0.00355 |
| Haiku 4.5 | $0.00177 | $0.00177 |
Grade A, and why
claude-mesh 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 7d 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 — 82 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.
What this is
claude-mesh is a networked messaging substrate for Claude Code instances: a self-hosted HTTP relay + per-Claude MCP channel server that lets Claudes on different machines DM, broadcast, thread, and approve tool-permissions for each other. Built on Anthropic's research-preview claude/channel MCP extension.
Status: software-complete and released. All 33 plan tasks are done; the relay ships as a Docker image (ghcr.io/pouriamrt/claude-mesh/relay, published on v*.*.* tags). Inbound <channel> tag delivery is verified against real Claude Code (v2.1.80+). Outbound permission_request relay is wired and unit-tested but not yet smoke-tested across two live Claude sessions. Remaining known gaps are listed in README §Caveats — keep that section honest when you change them.
The original design docs live in docs/superpowers/ (spec + 33-task plan) but docs/ is gitignored — local-only. README.md is the public source of truth.
Commands
The repo is a pnpm 10 workspace. Node 22 or 24 (25 lacks prebuilt better-sqlite3). Run from the repo root.
pnpm install # install all workspace deps
pnpm -r build # build every package
pnpm -r typecheck # tsc --noEmit across the workspace
pnpm -r exec vitest run # full suite (~191 tests; e2e L3 scenarios skip without CLAUDE_DRIVER)
pnpm -r test:ci # vitest run + coverage thresholds
# Scope to one package:
pnpm -F @claude-mesh/relay exec vitest run
pnpm -F @claude-mesh/shared exec vitest run channel # single test file
pnpm -F @claude-mesh/shared exec vitest run -t "round-trip" # single test name
# L3 end-to-end against a real claude binary:
CLAUDE_DRIVER=cli pnpm -F @claude-mesh/e2e exec vitest run
Coverage thresholds (enforced in each package's vitest.config.ts): 95% lines on shared, 85% on relay; peer-agent gates are lower (CLI entry points + SSE client excluded — exercised by the L3 harness instead).
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.
- 7d ago First seen · 82 lines · 1,774 tokens per session scan A 6a9fbbb02646
claude-mesh CLAUDE.md is an instructions file published in the GitHub repository pouriamrt/claude-mesh (23 stars, last pushed 1mo ago), licensed MIT. It adds 1,774 tokens to every session, about $0.0089 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-30.
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).
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).
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.