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/mavlink/qgroundcontrol/mavlink-includesgit clone --depth 1 https://github.com/mavlink/qgroundcontrolWhat 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.00615 | $0.00615 |
| Opus 5 | $0.00308 | $0.00308 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
qgroundcontrol mavlink-includes.instructions.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 2d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MAVLink Include Rules for Headers
C++ header files must use the lightest possible MAVLink include. Heavy includes in headers slow Qt moc parsing dramatically (~2.5s vs ~8ms per header).
Include Hierarchy (lightest to heaviest)
| Header | Provides | Preprocessed Lines |
|---|---|---|
MAVLinkEnums.h |
All 253 MAVLink enum typedefs (MAV_CMD, MAV_TYPE, MAV_RESULT, etc.) | ~5,500 |
MAVLinkMessageType.h |
mavlink_message_t, mavlink_channel_t, base types |
~2,700 |
QGCMAVLinkTypes.h |
FirmwareClass_t, VehicleClass_t, maxRcChannels |
~50 |
VehicleTypes.h |
MavCmdResultFailureCode_t, RequestMessageResultHandlerFailureCode_t |
~30 |
QGCMAVLink.h |
All of the above combined | ~8,300 |
MAVLinkLib.h |
Full MAVLink with all 387 message pack/unpack headers | ~180,000 |
Rules
-
Never include
MAVLinkLib.hin a.hfile unless the header uses specific MAVLink message struct types in its declarations (e.g.,mavlink_command_long_t,mavlink_command_ack_t). Move message struct usage to.ccfiles when possible. -
Never include
Vehicle.hjust for type aliases. UseVehicleTypes.h+class Vehicle;forward declaration instead, when onlyMavCmdResultFailureCode_torRequestMessageResultHandlerFailureCode_tare needed. -
Pick the lightest include that satisfies the header's needs:
- Only enum constants? →
MAVLinkEnums.h mavlink_message_tin signatures? →MAVLinkMessageType.h- Both enums and message type? →
MAVLinkEnums.h+MAVLinkMessageType.h(still lighter thanQGCMAVLink.h) FirmwareClass_t/VehicleClass_t? →QGCMAVLinkTypes.h
- Only enum constants? →
-
Headers must be self-contained. Every type used in a header's declarations must be provided by an explicit
#include, not by the precompiled header (PCH). The PCH providesMAVLinkLib.hfor.ccfiles, but moc processes headers independently. -
MAVLinkLib.his fine in.ccfiles — it's provided by the PCH anyway. Only header includes affect moc parse time.
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.
- 2d ago First seen · 36 lines · 615 tokens per session scan A 9a217119bff7
qgroundcontrol mavlink-includes.instructions.md is an instructions file published in the GitHub repository mavlink/qgroundcontrol (4,888 stars, last pushed today), licensed Apache-2.0. It adds 615 tokens to every session, about $0.0031 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
mavlink-mcp CLAUDE.md
Instructions for hieutachi/mavlink-mcp, covering claude.md, what this is, architecture, commands and environment.
ai-drone-toolkit AGENTS.md
AGENTS.md instructions for robotto-xyz/ai-drone-toolkit, covering agents.md — ai drone toolkit, 1. what this project is, 2. repository layout, setup & common commands and 3. non-negotiable principles.
nim_duilib CLAUDE.md
Instructions for rhett-lee/nim_duilib, covering nimduilib - 跨平台 c++ ui 库, 项目概述, 项目结构, 开发模式(xml + c++) and xml 布局文件.
bagel AGENTS.md
Instructions for Extelligence-ai/bagel, covering bagel for agents, set up bagel for a user, use bagel well and develop on bagel.
bagel CLAUDE.md
Instructions for Extelligence-ai/bagel: See AGENTS.md for setup, usage etiquette, and development workflow. It is the single source of truth for agent instructions in this repo.
ha-airspace CLAUDE.md
Instructions for ifnull/ha-airspace, covering claude.md, project at a glance, tech stack, code conventions and style.