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/forward-declarationsgit 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.00246 | $0.00246 |
| Opus 5 | $0.00123 | $0.00123 |
| Sonnet 5 | $0.00049 | $0.00049 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
qgroundcontrol forward-declarations.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.
What it actually says
Forward Declaration Rules for Headers
Prefer forward declarations and lightweight type headers over including full class definitions.
Vehicle.h
Vehicle.h is one of the heaviest headers in the codebase. Most headers that reference Vehicle only need:
- A pointer/reference to Vehicle →
class Vehicle;forward declaration - Vehicle type aliases →
#include "VehicleTypes.h"
Only include Vehicle.h if the header calls Vehicle methods, accesses Vehicle members, or inherits from Vehicle.
QGCMAVLink.h
QGCMAVLink.h combines MAVLink enums, message types, and QGC-specific type aliases. Most headers only need one of these. Use the specific lightweight header instead:
MAVLinkEnums.hfor enum constantsMAVLinkMessageType.hformavlink_message_tQGCMAVLinkTypes.hforFirmwareClass_t,VehicleClass_t
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 · 24 lines · 246 tokens per session scan A 3a75729a7a0c
qgroundcontrol forward-declarations.instructions.md is an instructions file published in the GitHub repository mavlink/qgroundcontrol (4,881 stars, last pushed 2d ago), licensed Apache-2.0. It adds 246 tokens to every session, about $0.0012 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.