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 skills add mavlink/qgroundcontrol --skill qt-cpp-reviewgit 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-cpp-review)<a href="https://agentmods.dev/skills/mavlink/qgroundcontrol/qt-cpp-review"><img src="https://agentmods.dev/badge/skills/mavlink/qgroundcontrol/qt-cpp-review/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/skills/mavlink/qgroundcontrol/qt-cpp-review"><img src="https://agentmods.dev/badge/skills/mavlink/qgroundcontrol/qt-cpp-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00086 | $0.04142 |
| Opus 5.5 | $0.00034 | $0.01657 |
| Sonnet 5.5 | $0.00017 | $0.00828 |
| Haiku 4.5 | $0.00009 | $0.00414 |
Grade A, and why
qt-cpp-review 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 1mo 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 — 463 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Qt Code Review
A structured, read-only code review skill for Qt6 C++ code that combines deterministic linting with parallel agent-driven deep analysis across six focused domains.
When to use this skill
- When the user mentions review-related tasks: "review", "check", "audit", "look over", "code review", "sanity check"
- Suggest running this skill before committing code
- When the user asks to validate Qt6 C++ code quality
Arguments
/qt-cpp-review— review using universal Qt6 C++ rules only/qt-cpp-review framework— also apply Qt framework/module development rules (BC, exports, d-pointers, qdoc, QML versioning)
Framework mode detection
If $ARGUMENTS contains "framework", enable framework mode.
If the argument is not passed, auto-detect by scanning the first
few files in scope for framework signals. If two or more of
the following are found, suggest to the user:
"This looks like Qt framework/module code. Run
/qt-cpp-review framework to also apply framework-specific
rules (BC, exports, qdoc, QML versioning)?"
Framework signals (any two = likely framework code):
QT_BEGIN_NAMESPACE/QT_END_NAMESPACEQ_CORE_EXPORT,Q_GUI_EXPORT,Q_WIDGETS_EXPORT, or anyQ_*_EXPORTmacro#include <QtModule/private/*_p.h>(private headers)Q_DECLARE_PRIVATE,Q_D(),Q_Q()qt_internal_add_moduleorqt_add_modulein CMakeLists.txtsync.profileor.qmake.confin the repository root
Do not auto-enable framework mode — only suggest it. Let the user confirm.
When framework mode is enabled:
- Pass
--frameworkto the linter (if supported) - Load
references/qt-framework-checklist.mdalongside the universal checklist - Include framework rules in each agent's mission context
Scope detection
Detect the user's intended scope from their language:
Diff/commit scope (narrow)
Triggered by language like: "this commit", "these changes", "the diff", "what I changed", "my changes", "staged changes", "outstanding changes", "before I commit"
What ships with it
7 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.
- 1mo ago First seen · 463 lines · 86 tokens per session scan A ca52fa54c1ef
qt-cpp-review is a skill published in the GitHub repository mavlink/qgroundcontrol (5,041 stars, last pushed today), licensed Apache-2.0. It adds 86 tokens to every session and 4,142 once invoked, about $0.0003 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 skills, from other repositories
qt-cpp-review
Invoke when the user asks to review, check, audit, or look over Qt6 C++ code — or suggest before committing. Runs deterministic linting (60+ rules) then six parallel deep- analysis agents covering model contracts, ownership, threading, API correctness, error handling, and performance. Reports only high-confidence…
cpp-coding-standards
C++ coding standards based on the C++ Core Guidelines (isocpp.github.io). Use when writing, reviewing, or refactoring C++ code to enforce modern, safe, and idiomatic practices.
frama-c-proofreader
Verify and proofread C code with ACSL using this repository's Frama-C MCP workflow, Frama-C WP static proof, EVA alarms, and optional E-ACSL runtime checks. Use when asked to run Frama-C, check ACSL contracts, explain WP goals, inspect EVA alarms, validate C annotations, or state what a C proof does and does not…
ia-c-systems
C patterns for systems code, libraries, and native extensions: module layout, function decomposition, status-enum errors, memory safety, undefined behavior, and performance measurement. Use when writing, reviewing, refactoring, or debugging C, working with malloc lifetimes, buffer overflows, sanitizers, or Valgrind…
code-reviewer
A code-review procedure for Python, JavaScript, and Go programs. It checks security, performance, maintainability, naming, error handling, and testing.
review-ocaml
Two-phase review of an OCaml project. Use when the user asks to review an OCaml codebase, audit its module interfaces, restructure or redocument .mli files, or hunt for redundancy, dead code and optimisation opportunities across implementations. Phase one reads only dune and .mli files to judge the public interfaces…