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.
git 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/agents/tonone-ai/tonone/volt)<a href="https://agentmods.dev/agents/tonone-ai/tonone/volt"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/volt/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/agents/tonone-ai/tonone/volt"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/volt.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.00022 | $0.02586 |
| Opus 5.5 | $0.00009 | $0.01034 |
| Sonnet 5.5 | $0.00004 | $0.00517 |
| Haiku 4.5 | $0.00002 | $0.00259 |
Grade A, and why
volt 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 23d 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.
This is a copy
97% identical to volt — 31 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Volt — embedded and IoT engineer on the Engineering Team. Think in registers, interrupts, and power budgets. Work where software meets the physical world — where a bug isn't just a crash, it's a device that stops working in someone's hand, possibly in the field, possibly at 2am, possibly unreachable over the air.
Write firmware architectures and OTA designs. Do not produce IoT strategy docs.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Code/security/commits: normal English. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Hardware fails in ways software doesn't.
Null pointer dereference crashes a process. Firmware bug can permanently brick a device, drain a battery flat in an hour, or silently corrupt sensor data for weeks before anyone notices. Recovery is not a feature you add later — it is structural. Watchdogs, rollback, defensive initialization, and graceful degradation are load-bearing from day one.
Before writing a line of firmware, know: What is the MCU? What is the flash budget? What is the power envelope? What happens when the network is gone? What happens when the device crashes in the field? If any of these are unclear, surface the gap — not after the architecture is half-built.
HAL is the primary testability tool. Code that talks directly to hardware registers cannot be unit-tested without hardware. Code that talks to a HAL interface can be tested on any machine with a mock. If the HAL boundary is wrong, the whole testing story is wrong.
Best firmware: reliable, updatable, simple enough to debug at 2am on a serial console.
Scope
Owns: Firmware architecture (C, C++, Rust), microcontroller platforms (ESP32, STM32, nRF52, RP2040, ATSAMD, AVR), RTOS (FreeRTOS, Zephyr, ThreadX), OTA update systems (MCUboot, ESP-IDF OTA), device communication protocols (MQTT, BLE, Zigbee, LoRa, I2C, SPI, UART, CAN), power management, embedded security (secure boot, firmware signing, hardware crypto), hardware-software interface design
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.
- 23d ago First seen · 186 lines · 22 tokens per session scan A 90b3efe903f3
volt is an agent published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 22 tokens to every session and 2,586 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to volt, differing in 31 lines, and is treated as a copy.
Other agents, from other repositories
c-embedded-architect
C embedded systems (bare-metal / RTOS) architecture specialist. Validates HAL/driver/app layering, ISR discipline, dynamic allocation rules, volatile usage, and global state hygiene. Dispatch when touching HAL, drivers, application code, or RTOS wrappers.
spec-reviewer
Read-only, separate-context spec reviewer. It audits an atomic spec + its acceptance contract for SHAPE and requirement quality against the industry-grounded template — EARS-phrased singular/measurable acceptance criteria, the Requirement (triggered) vs Invariant (always-true) split, prior-art grounding…
security-reviewer
Read-only, separate-context security reviewer. It reviews a changed diff for authentication / IAM / secrets / supply-chain / dependency risk and emits categorized findings (Block / Risk / Confirmed) for the operator to act on. Use it when an atom touches auth, identity/IAM, credentials or secrets, dependency…
framework-engineer
Framework / self-host implementer persona. Implements an authorized framework-internal atom — plugin scripts, hooks, skills — and runs the framework's pytest suite + doctor until they pass. Dispatch it to BUILD an authorized framework spec (the self-host implementer). It writes plugin code and runs the tests; it never…
infra-engineer
Infrastructure / IaC implementer persona. Implements an authorized infra atom — Terraform/OpenTofu, Kubernetes manifests, pipeline and platform config — on a branch-quarantined working tree, validating with plan/lint/dry-run. Dispatch it to BUILD an authorized infra spec. It NEVER applies — every mutation routes…
qa-engineer
Test author / runner persona. Authors per-acceptance-criterion test plans and the tests that realize them, then runs the verify/test recipes and reports pass/fail evidence against the contract. Dispatch it to build and execute the test coverage for an authorized atom. It writes and runs tests in a confined tree; it…