QGroundControl is a cross-platform ground control station for unmanned aircraft, allowing operators to control MAVLink-enabled drones and plan their missions. Drone users work with it to monitor flights, configure vehicles, tune parameters, stream video, and manage autonomous missions, while the catalogue contains skills and instructions for using the application.
Borrowing it
Nothing to install: this file belongs to mavlink/qgroundcontrol. 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/mavlink/qgroundcontrol/master/.github/instructions/mavlink-includes.instructions.mdgit clone --depth 1 https://github.com/mavlink/qgroundcontrolWrote 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/mavlink/qgroundcontrol/mavlink-includes)<a href="https://agentmods.dev/instructions/mavlink/qgroundcontrol/mavlink-includes"><img src="https://agentmods.dev/badge/instructions/mavlink/qgroundcontrol/mavlink-includes/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.
<a href="https://agentmods.dev/instructions/mavlink/qgroundcontrol/mavlink-includes"><img src="https://agentmods.dev/badge/instructions/mavlink/qgroundcontrol/mavlink-includes.svg" alt="Reviewed on agentmods" width="80" 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.00763 | $0.00763 |
| Opus 5.5 | $0.00305 | $0.00305 |
| Sonnet 5.5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00076 | $0.00076 |
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 5d 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 — 38 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) and every translation unit that includes them. MAVLinkLib.h skips the dialect under moc (Q_MOC_RUN), so moc sees only the MAVLinkMessageType.h base types from it.
Include Hierarchy (lightest to heaviest)
| Header | Provides | Preprocessed Lines |
|---|---|---|
QGCMAVLinkTypes.h |
FirmwareClass_t, VehicleClass_t, maxRcChannels |
~50 |
MAVLinkMessageType.h |
mavlink_message_t, mavlink_channel_t, base types |
~2,700 |
MAVLinkEnums.h |
All MAVLink enum typedefs (MAV_CMD, MAV_TYPE, MAV_RESULT, etc.), generated at build time | ~5,500 |
VehicleTypes.h |
MavCmdResultFailureCode_t, RequestMessageResultHandlerFailureCode_t (includes MAVLinkEnums.h and QGCMAVLinkTypes.h) |
~5,500 |
QGCMAVLink.h |
MAVLinkEnums.h, MAVLinkMessageType.h, and QGCMAVLinkTypes.h combined |
~8,300 |
MAVLinkLib.h |
Full MAVLink with every message pack/unpack header | ~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.
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.
- 5d ago Changed · +42 tokens per session 06dddfce357e
- 6d ago Changed · +2 lines · +106 tokens per session 623fa5660720
- 2mo 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 (5,075 stars, last pushed today), licensed Apache-2.0. It adds 763 tokens to every session, about $0.0031 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-30.
Other instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.