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/ipnet-mesh/meshcore-mqtt/claude-mdgit clone --depth 1 https://github.com/ipnet-mesh/meshcore-mqttWrote 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/ipnet-mesh/meshcore-mqtt/claude-md)<a href="https://agentmods.dev/instructions/ipnet-mesh/meshcore-mqtt/claude-md"><img src="https://agentmods.dev/badge/instructions/ipnet-mesh/meshcore-mqtt/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.00005 | $0.00005 |
| Opus 5 | $0.00003 | $0.00003 |
| Sonnet 5 | $0.00001 | $0.00001 |
| Haiku 4.5 | $0.00001 | $0.00001 |
Grade A, and why
meshcore-mqtt 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 6d 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 6d ago First seen · 2 lines · 5 tokens per session scan A 336cc4fbf19b
meshcore-mqtt CLAUDE.md is an instructions file published in the GitHub repository ipnet-mesh/meshcore-mqtt (41 stars, last pushed 9mo ago), licensed GPL-3.0. It adds 5 tokens to every session, about $0.0000 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
iot-dc3 AGENTS.md
AGENTS.md instructions for pnoker/iot-dc3, covering agents.md, scope and precedence, sources of truth, project overview and repository map.
iot-dc3 CLAUDE.md
Claude Code instructions for pnoker/iot-dc3: This file provides guidance to AI coding assistants when working with code in this repository.
AetherEdge AGENTS.md
Instructions for EvanL1/AetherEdge, covering aetheredge agent instructions, product direction, repository map, architecture boundaries and ai safety.
AetherEdge CLAUDE.md
Instructions for EvanL1/AetherEdge, a project described as: Deterministic edge runtime for agent-configured physical spaces — Kernel, CLI, and SDK for AetherIoT.
AetherEdge GEMINI.md
Instructions for EvanL1/AetherEdge, a project described as: Deterministic edge runtime for agent-configured physical spaces — Kernel, CLI, and SDK for AetherIoT.
core integrations.instructions.md
Instructions for home-assistant/core, covering file locations, general guidelines, entity platforms, integration quality scale and how rules apply.