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 skillgit 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)<a href="https://agentmods.dev/skills/raylanlin/smarttune-cli/skill"><img src="https://agentmods.dev/badge/skills/raylanlin/smarttune-cli/skill/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"><img src="https://agentmods.dev/badge/skills/raylanlin/smarttune-cli/skill.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.00056 | $0.02971 |
| Opus 5.5 | $0.00022 | $0.01188 |
| Sonnet 5.5 | $0.00011 | $0.00594 |
| Haiku 4.5 | $0.00006 | $0.00297 |
Grade A, and why
smarttune 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SmartTune CLI (stune)
Multi-platform flight log analysis & tuning advisor. Supports ArduPilot (.bin/.log onboard, .tlog telemetry), Betaflight (.bbl/.bfl), and PX4 (.ulg).
Platform is auto-detected from the log file format.
Installation
cd ~/cli-tools/smarttune-cli
pip install -e .
Quick Reference
# Comprehensive analysis (recommended) — PID + FFT + Filter + Mag
stune analyze -i log.bin
# Log quality scoring — data completeness / excitation / sample rate
stune quality -i log.bin
# Individual analyses
stune pid -i log.bin -a roll
stune fft -i log.bin
stune filter -i log.bin --gyro-filter 40 --visual
stune sysid -i log.bin -a roll
stune hardware -i log.bin
stune magfit -i log.bin
# Telemetry log from a ground station (lower rate, no PID terms — limits are reported)
stune quality -i "2026-09-13 10-00-00.tlog"
stune analyze -i flight.tlog -f json | jq '.telemetry_notes'
# List supported platforms
stune platforms
Usage Rules
- Check help first:
stune <command> --helpwhen unsure about flags - Terminal output by default: no
-oflag → stdout only - Optional charts: add
--visualfor matplotlib plots - Cleanup after analysis: delete raw
.bin/.log/.tlog/.bbl/.ulgfiles after processing - ⚠️ A
.tlogis a screening source, not a tuning source. Telemetry recordings carry no rate-controller terms and a 1–50 Hz gyro stream. Whentelemetry_notesis present in the result, repeat those limits to the user and do not present PID or vibration numbers from a.tlogas tuning-grade — ask for the onboard.bininstead. - ⚠️ MANDATORY: Validate parameters before recommending. After analysis generates tuning suggestions, you MUST verify each parameter exists in the target firmware by running:
If validation fails (exit code 1), do NOT recommend that parameter — it may not exist in the firmware, the value may be outside [min, max], or (for an enum) not a defined member. When the rejection lists allowed values, pick from those. Find an alternative or tell the user the parameter is not available.stune params --validate <PARAM_NAME> <VALUE> -p <platform>
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 · +8 lines · +5 tokens per session 6b2629b99ec7
- 1mo ago First seen · 319 lines · 51 tokens per session scan A 660d31573324
smarttune is a skill published in the GitHub repository raylanlin/smarttune-cli (31 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 2,971 once invoked, about $0.0002 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…