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 raylanlin/smarttune-cli --skill skill-mcpgit clone --depth 1 https://github.com/raylanlin/smarttune-cliWrote 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/raylanlin/smarttune-cli/skill-mcp)<a href="https://agentmods.dev/skills/raylanlin/smarttune-cli/skill-mcp"><img src="https://agentmods.dev/badge/skills/raylanlin/smarttune-cli/skill-mcp/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/raylanlin/smarttune-cli/skill-mcp"><img src="https://agentmods.dev/badge/skills/raylanlin/smarttune-cli/skill-mcp.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.03192 |
| Opus 5.5 | $0.00034 | $0.01277 |
| Sonnet 5.5 | $0.00017 | $0.00638 |
| Haiku 4.5 | $0.00009 | $0.00319 |
Grade A, and why
smarttune-mcp 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SmartTune MCP
Use this skill when SmartTune is connected through MCP and the agent does not have shell, exec, or write permission.
This is the MCP-only variant of the SmartTune skill. If the agent has normal CLI access, use the smarttune skill instead.
Hard Rules
- Do not call
exec, shell commands, Python subprocesses, or thestuneCLI. - Do not ask for write, edit, or process execution permissions to analyze a log.
- Do not create report files or choose arbitrary output paths.
- Do not modify logs, parameters, firmware, local files, or aircraft configuration.
- Use only the SmartTune MCP tools listed below.
- If these tools are unavailable, say SmartTune MCP is not connected and ask the operator to enable the MCP server.
- Analysis results arrive pre-validated (v3.2.1). Every recommendation returned by
smarttune_analyze_logand the per-module analysis tools carriesvalidated/validation_status. Only recommendations withvalidated: truemay be presented as-is; afalseentry must be dropped or corrected using theoptionsfromsmarttune_get_param. - MANDATORY: Validate every value YOU adjusted. Before suggesting any parameter change, call
smarttune_validate_paramwith the exact parameter name, proposed value, and platform. Never recommend a parameter that fails validation — search for alternatives withsmarttune_search_params. Averdictofunverifiableis not approval. For a whole set of adjusted values, usesmarttune_validate_params(one call instead of N). - Every tool returns one shape:
{ok: true, ...}on success,{ok: false, error_code, message, hint, retryable}on failure. A rejected parameter value is a successful call withvalid: false. - Firmware-version tables (v3.3). All six parameter tools accept
fw_version(e.g."copter-4.5"); omit it for the platform default (ArduPilot default = Copter-4.1). An unknown version returnserror_code: "E4011"with the available list. Ranges can differ between versions — validate against the version the user actually flies. - Never list a whole parameter table. Browse with
smarttune_list_param_groups→smarttune_list_params(group=...)→smarttune_get_param(name)for full detail. ArduPilot alone is ~2,800 parameters.
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 Changed · +6 lines 3fb1886594e7
- 1mo ago First seen · 172 lines · 86 tokens per session scan A 759f18547eba
smarttune-mcp is a skill published in the GitHub repository raylanlin/smarttune-cli (31 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 3,192 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
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. Read-only triage through the bagel MCP tools.
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.
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).
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.
opentrons-integration
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
pylabrobot
Vendor-agnostic lab automation framework. Use when controlling multiple equipment types (Hamilton, Tecan, Opentrons, plate readers, pumps) or needing unified programming across different vendors. Best for complex workflows, multi-vendor setups, simulation. For Opentrons-only protocols with official API…