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.
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 skills/mavlink/qgroundcontrol/qt-qml-docsnpx skills add mavlink/qgroundcontrol --skill qt-qml-docsgit 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/skills/mavlink/qgroundcontrol/qt-qml-docs)<a href="https://agentmods.dev/skills/mavlink/qgroundcontrol/qt-qml-docs"><img src="https://agentmods.dev/badge/skills/mavlink/qgroundcontrol/qt-qml-docs.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 | $0.00150 | $0.02192 |
| Opus 5 | $0.00075 | $0.01096 |
| Sonnet 5 | $0.00030 | $0.00438 |
| Haiku 4.5 | $0.00015 | $0.00219 |
Grade A, and why
qt-qml-docs 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QML Documentation Skill
You are an expert in Qt/QML who writes clear, accurate, developer-friendly reference documentation for QML components. Your task is to read QML source files — along with any related files (C++ backends, QML modules, resource files, CMakeLists.txt, qmldir, etc.) — and produce structured Markdown reference docs that give developers a complete picture of how components fit into the project.
Core requirements
- No code snippets (except Usage Example). Do not wrap any code in markdown code fences, except in the Usage Example section (Section 8) for reusable components — see below. Describe code behaviour, method signatures, and property types in prose and tables instead.
- Context-aware. Understand how each component fits into the project: what the application/module does, what role this component plays, and what it depends on.
- Tables for properties. Always use Markdown tables (not bullet lists) to document properties.
- Follow project conventions. Infer and respect any QML development conventions from the project's documentation or code patterns.
Document structure
For each QML component, generate a Markdown file named <ComponentName>.md with the following sections (omit any section that has no content):
1. Component Overview
Describe what the application or module does and where this component fits in the project architecture. Then explain what this specific component does — its visual or logical role, when a developer would reach for it, and what problem it solves. Keep this concise: a developer new to the codebase should understand the component's purpose at a glance.
2. Project Structure and Dependencies
Explain how the component relates to the project:
- What files import or instantiate it?
- What does it import (Qt Quick modules, custom project QML types, C++ registered types)?
- For custom QML types, describe what they provide and where they come from.
- Relevant build or module requirements (e.g. CMake targets, qmldir, qmltypes).
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 185 lines · 150 tokens per session scan A d6a02bd7ed38
qt-qml-docs is a skill published in the GitHub repository mavlink/qgroundcontrol (4,896 stars, last pushed today), licensed Apache-2.0. It adds 150 tokens to every session and 2,192 once invoked, about $0.0007 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 skills, from other repositories
drone_commands
Execute drone commands -- the AIPass CLI interface for all module operations.
authoring-pipelines
Use when the user wants a bagel data pipeline — reducing a log to windows around events ("keep 30s around every hard brake"), recurring snippets/GIFs/exports, or any tasks-and-gates automation over robot data.
exporting-visualizations
Use when the user wants to SEE robot data — visualize, plot, replay, or export a log or query result from bagel to a viewer or training format (Rerun, Lichtblick, PlotJuggler, LeRobot).
operating-live-sinks
Use when subscribing to live robot data (MQTT, rosbridge) through bagel, managing standing pipelines that survive restarts, or when questions about live-buffer sizes and disk usage come up.
triaging-robot-logs
Use when investigating a robot log or flight log with bagel — finding events, anomalies, or "what happened around X" in rosbags, MCAP, CAN, MDF4, ULog, or Betaflight files. Routes to the server's triage capability.
qt-cpp-review
Qt6/C++ deep code review for Serial Studio. Use when asked to "review", "audit", "check", "look over", or "sanity check" C++ — or before committing. Runs the repo linter (scripts/code-verify.py) as Phase 1, then six parallel read-only analysis agents covering Qt model contracts, ownership/lifecycle, thread-safety +…