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/agents-mdgit clone --depth 1 https://github.com/ipnet-mesh/meshcore-mqttWhat 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.04614 | $0.04614 |
| Opus 5 | $0.02307 | $0.02307 |
| Sonnet 5 | $0.00923 | $0.00923 |
| Haiku 4.5 | $0.00461 | $0.00461 |
Grade A, and why
meshcore-mqtt 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 yesterday.
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.
- yesterday First seen · 505 lines · 4,614 tokens per session scan A 690ed15d23e7
meshcore-mqtt AGENTS.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 4,614 tokens to every session, about $0.0231 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
core integrations.instructions.md
Instructions for home-assistant/core, covering file locations, general guidelines, entity platforms, integration quality scale and how rules apply.
core copilot-instructions.md
Copilot instructions for home-assistant/core, covering copilot code review instructions, pull request template, breaking change, proposed change and type of change.
core CLAUDE.md
Claude Code instructions for home-assistant/core, a project described as: :housewithgarden: Open source home automation that puts local control and privacy first.
core AGENTS.md
AGENTS.md instructions for home-assistant/core, covering github copilot & claude code instructions, git commit guidelines, pull requests, development commands and python syntax notes.
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.