meshcore-mcp: Instructions file for Codex

AGENTS.md

meshcore-mcp AGENTS.md is an instructions file for Codex, OpenCode from dpup/meshcore-mcp. It costs 2,794 tokens per session, scanned A, original, MIT.

A project instruction file for agents and developers working on meshcore-mcp. The project is an MCP server, meaning it gives AI applications structured access to a MeshCore device and its reachable mesh network.

In plain words
What is it for?
Orienting contributors to the repository, its agent contracts, remote administration details, documentation layers, and device-focused architecture.
Why use it?
It explains the project's purpose, boundaries, documentation structure, companion projects, and the rules agents must follow.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Claude Code; mentions AGENTS.md.

This is dpup/meshcore-mcp's own configuration. It tells Codex and OpenCode how to work on meshcore-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything meshcore-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to dpup/meshcore-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dpup/meshcore-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/dpup/meshcore-mcp

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for meshcore-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/dpup/meshcore-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/dpup/meshcore-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/dpup/meshcore-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/dpup/meshcore-mcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for meshcore-mcp AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/dpup/meshcore-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/dpup/meshcore-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,794 This file is loaded in full into every session.
When invoked 2,794 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02794 $0.02794
Opus 5.5 $0.01118 $0.01118
Sonnet 5.5 $0.00559 $0.00559
Haiku 4.5 $0.00279 $0.00279

Measured 2mo ago against content hash cfbd3af3ae63, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

meshcore-mcp AGENTS.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 2mo 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.

AGENTS.md · 196 lines

How it starts

The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Guidance for AI agents (and humans) working on meshcore-mcp. Keep this current when architecture or conventions change.

What this is

A Model Context Protocol (MCP) server that exposes a MeshCore node — and the mesh reachable through it — as a clean, high-signal surface of tools, resources, and prompts for any MCP client (Claude Code, or meshcore-elmer's bridge). It is the device layer, and ungated by design: it contains no conversation policy, admin-channel gate, or autonomous behavior (that belongs to meshcore-elmer). See docs/plans/ for the PRD (v0.3) and execution plan.

Docs are three layers: README.md (landing + the Claude Code MCP-config snippet

  • the tool/resource/prompt tables), docs/guide.md (hand-written concepts & recipes), and docs/api.md (generated by TypeDoc); llms.txt indexes all three for agents.

Companion projects, by the same author — keep all three consistent in stack, style, and tone:

  • @dpup/meshcore-ts — the typed device client this server is built on (runtime dependency).
  • @dpup/meshcore-sim — the deterministic simulator we test and demo against (dev dependency; never shipped).

The two contracts (read this first)

meshcore-mcp is a thin server wedged between two contracts it does not own.

Below — @dpup/meshcore-ts. The server holds one persistent MeshCoreClient (autoSync: true) and consumes its normalized surface: named events (contactMessage, channelMessage, channelData, advert, …), typed models, hex-string keys, Date timestamps, typed errors. It never touches @liamcottle/meshcore.js directly. MeshService takes its MeshCoreClient by injection — production builds MeshCoreClient.tcp(host, port); tests build new MeshCoreClient(sim.asConnection()). Nothing below MeshService knows which.

Above — MCP, via @modelcontextprotocol/sdk's McpServer: tools (registerTool, Zod schemas, annotations), resources (registerResource, the subscribable live stream), prompts (registerPrompt), over a StdioServerTransport.

Read the full file on GitHub · 196 lines

Changes

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.

  1. 2mo ago First seen · 196 lines · 2,794 tokens per session scan A cfbd3af3ae63

Subscribe to this mod's changes

meshcore-mcp AGENTS.md is an instructions file published in the GitHub repository dpup/meshcore-mcp (2 stars, last pushed 5mo ago), licensed MIT. It adds 2,794 tokens to every session, about $0.0112 per session on Opus 5.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.

Related

meshcore-mcp AGENTS.md compared with instructions from other repositories

meshcore-mcp AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
meshcore-mcp AGENTS.mddpup/meshcore-mcpInstructions file25mo agoMITA2,794Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,649GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA2,022GitHub Copilot