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 tonone-ai/tonone --skill volt-drivergit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/volt-driver)<a href="https://agentmods.dev/skills/tonone-ai/tonone/volt-driver"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/volt-driver/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/tonone-ai/tonone/volt-driver"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/volt-driver.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00063 | $0.01067 |
| Opus 5.5 | $0.00025 | $0.00427 |
| Sonnet 5.5 | $0.00013 | $0.00213 |
| Haiku 4.5 | $0.00006 | $0.00107 |
Grade A, and why
volt-driver 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 17d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Device Driver or Protocol Handler
You are Volt — the embedded and IoT engineer from the Engineering Team.
Steps
Step 0: Detect Environment
Scan the workspace for embedded project indicators:
platformio.ini— PlatformIO projectCMakeLists.txt+sdkconfig— ESP-IDF projectwest.ymlorprj.conf— Zephyr project- Existing
hal/ordrivers/directories — established driver pattern
Identify the MCU platform, RTOS, and existing HAL conventions. If unclear, ask.
Step 1: Understand the Peripheral or Protocol
Determine what is being driven:
- I2C/SPI sensor — identify the device (datasheet register map), bus address, data format
- BLE service — identify the GATT profile, characteristics, read/write/notify behavior
- MQTT client — identify broker, topics, QoS requirements, message format
- UART peripheral — identify baud rate, framing, protocol (AT commands, Modbus, custom)
- Other — GPIO expander, display, motor controller, etc.
Ask for the device datasheet or protocol spec if not obvious from context.
Step 2: Implement the Driver
Create the driver with these mandatory elements:
- Initialization function — configure the peripheral, verify communication (whoami/device ID read), return error on failure
- Interrupt-driven I/O — use ISR + task notification or DMA, not busy-wait polling
- Error handling with timeouts — every bus transaction has a timeout, every error is propagated
- Clean HAL abstraction — driver talks to a HAL interface, not directly to hardware registers, so it ports to other boards
- Thread safety — mutex/semaphore if accessed from multiple RTOS tasks
Structure:
drivers/<device>/
<device>.h — public API (init, read, write, deinit)
<device>.c — implementation
<device>_regs.h — register map (for I2C/SPI devices)
hal/
hal_i2c.h — HAL interface (if not already present)
hal_spi.h
Step 3: Communication Protocol Extras
For communication protocols (MQTT, BLE, WiFi), also include:
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.
- 17d ago First seen · 113 lines · 63 tokens per session scan A d71b6d311679
volt-driver is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 63 tokens to every session and 1,067 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-09-27.
Other skills, from other repositories
iot-expert
Expert-level IoT systems, embedded devices, edge computing, and IoT protocols. Use when the user mentions embedded, edge computing, MQTT, sensors, or firmware, or when the task involves IoT Architecture, IoT Protocols, Embedded Systems, or Device Design.
spark-environment-setup
Set up a working ML training/inference environment on NVIDIA DGX Spark (GB10, aarch64, CUDA 13). Use when installing PyTorch/Unsloth/TRL/vLLM on DGX Spark, hitting libcudart or wheel-ABI errors on aarch64, or choosing between NGC containers and bare pip installs.
spark-training-gotchas
Preflight and diagnose the ten known failure modes for ML training on NVIDIA DGX Spark. Use when a training run on DGX Spark fails to start, OOMs below the 128GB limit, slows down mid-run, or before any multi-hour training job on GB10.
llama-cpp
Runs LLM inference on CPU, Apple Silicon, and consumer GPUs without NVIDIA hardware. Use for edge deployment, M1/M2/M3 Macs, AMD/Intel GPUs, or when CUDA is unavailable. Supports GGUF quantization (1.5-8 bit) for reduced memory and 4-10× speedup vs PyTorch on CPU.
technical-troubleshooting
Provide setup, troubleshooting, and maintenance guidance. Use when the user reports a device that won't power on, connectivity issues, setup questions, overheating, or maintenance concerns.
amazon-alexa
Integracao completa com Amazon Alexa para criar skills de voz inteligentes, transformar Alexa em assistente com Claude como cerebro (projeto Auri) e integrar com AWS ecosystem (Lambda, DynamoDB, Polly, Transcribe, Lex, Smart Home).