Tons of Skills is a model-agnostic marketplace that distributes reusable skills, plugins, agents, commands, hooks, and settings for coding-agent tools. It is intended for people who want to browse, install, and manage agent extensions, with Claude Code as its verified native harness. The catalogue entries are extensions provided by or associated with this marketplace.
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/jeremylongshore/tons-of-skills-marketplaceWrote 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/jeremylongshore/tons-of-skills-marketplace/volt)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/volt"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/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/jeremylongshore/tons-of-skills-marketplace/volt"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/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.00067 | $0.02810 |
| Opus 5.5 | $0.00027 | $0.01124 |
| Sonnet 5.5 | $0.00013 | $0.00562 |
| Haiku 4.5 | $0.00007 | $0.00281 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- volt — 97% identical, 31 lines differ
How it starts
The opening of the file, as written. The whole thing — 211 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.
- 1mo ago First seen · 211 lines · 67 tokens per session scan A 659c53c05f28
volt is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,876 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 2,810 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-03.
Other agents, from other repositories
iot-protocol-engineer
Use this agent when choosing or designing connectivity for a device: MQTT, CoAP, LwM2M, BLE GATT, LoRaWAN, Thread, or Zigbee selection, topic and QoS design, power budgets, TLS or DTLS, or debugging disconnects and latency. It walks the constraint matrix before recommending a protocol, then designs the protocol layer…
bus-driver-engineer
Use this agent when writing, porting, or debugging an I2C, SPI, UART, CAN, or USB driver: a stuck bus or reads of 0xFF, choosing DMA, interrupt, or polled transfers, baud rate and CAN bit timing math, error recovery, or peripheral quirks on STM32, NXP, Nordic, and ESP32. It returns the init sequence, sync and async…
rtos-engineer
Use this agent when designing or debugging multi-task firmware on FreeRTOS or Zephyr: task graphs and priorities, queue and buffer sizing, priority inversion, stack sizing, watchdog strategy, ISR-to-task hand-off, or porting between the two. It asks for real rates and deadlines, then returns a task graph with…
bare-metal-engineer
Use this agent when writing firmware without a HAL: register-level drivers, linker scripts, startup code, a minimal runtime without the standard library, compiler flags, volatile and memory barrier questions, or reading a map file. It works directly against peripheral registers with arm-none-eabi-gcc and explains the…
bootloader-engineer
Use this agent when designing or reviewing a bootloader: primary, secondary, and golden image topologies, image headers, flash erase and program sequences, CRC32 and ECDSA signature checks with mbedTLS, the jump to the application, or OTP-based rollback prevention. It returns a flash layout, a boot decision tree, the…
fpga-engineer
Use this agent when an MCU has to talk to an FPGA: AXI-Lite or SPI register banks in Verilog, Vivado or Quartus flows, XDC timing constraints, the MCU-side driver, or choosing the MCU-FPGA interface. It returns the register map, the Verilog module, the constraints, and the MCU driver.